This almost worked for me, except that the menus are not correctly drawn; the font appears to be the correct, larger size, but the menus themselves don't appear to have grown to accommodate the larger font.
Any thoughts? On 22 March 2014 14:14, Uli Schlachter <[email protected]> wrote: > Hey, > > On 22.03.2014 11:30, Dan Milon wrote: > > I installed archlinux & awesome on a macbook pro with a retina > > display. As you can imagine everything was super tiny. I added "Xft.dpi > > = 196" to xrdb and now gtk, qt etc apps display normally, but the awesome > > status bar still shows tiny. > > > > It seems that awesome itself is unaffected by "Xft.dpi". > > Do you have any idea what I could do to fix this? > > No idea if this actually works, but (if you are using 3.5, which I think > you > are), you could try adding the following to the *beginning* (beginning is > the > very first line of your config, not later) of your rc.lua: > > require("lgi").PangoCairo.font_map_get_default():set_resolution(196) > > Please tell me if this has any effect. > > Uli > > > P.S.: For future-Uli: Google knows about gdk_screen_get_resolution() and > Debian > code search figured out that this function is used in a call to > pango_cairo_context_set_resolution() inside > gtk_widget_update_pango_context(). > > P.P.S.: It would be nice to figure out if lgi let's us use > gdk_screen_get_resolution() and gdk_screen_get_font_options() so that they > can > be used in wibox.widget.textbox. No idea how yet, but if we figure out a > way to > map gdk screens to awesome screens, that could be used for implementing > this > "properly". Or we just link awesome against Gdk and use this code properly > and > get rid of awesome's screens, but that might result in a fight about who > owns > the X11 connection... > -- > Who needs a ~/.signature anyway? > > -- > To unsubscribe, send mail to [email protected]. >
