interesting
/
libui
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Removed the DPI fields from uiAreaDrawParams. We no longer worry about DPI.

This commit is contained in:
Pietro Gagliardi 2015-10-13 19:44:16 -04:00
parent 7d8c78bf8e
commit 2cbbc6c69d
3 changed files with 0 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
darwin/area.m
View File

@ -130,8 +130,6 @@ uiDarwinDefineControl(
dp.ClipWidth = r.size.width;
dp.ClipHeight = r.size.height;
// TODO DPI
av = (areaView *) [self superview];
dp.HScrollPos = [av hscrollPos];
dp.VScrollPos = [av vscrollPos];

3
ui.h
View File

@ -283,9 +283,6 @@ struct uiAreaDrawParams {
intmax_t ClipWidth;
intmax_t ClipHeight;
int DPIX;
int DPIY;
intmax_t HScrollPos;
intmax_t VScrollPos;
};

8
unix/area.c
View File

@ -167,14 +167,6 @@ static gboolean areaWidget_draw(GtkWidget *w, cairo_t *cr)
dp.ClipWidth = clipX1 - clipX0;
dp.ClipHeight = clipY1 - clipY0;
// on GTK+ you're not supposed to care about high-DPI scaling
// instead, pango handles scaled text rendering for us
// this doesn't handle non-text cases, but neither do other GTK+ programs, so :/
// wayland and mir GDK are hardcoded to 96dpi; X11 uses this as a fallback
// thanks to hergertme in irc.gimp.net/#gtk+ for clarifying things
dp.DPIX = 96;
dp.DPIY = 96;
dp.HScrollPos = gtk_adjustment_get_value(ap->ha);
dp.VScrollPos = gtk_adjustment_get_value(ap->va);