1. 16 Jul, 2022 1 commit
  2. 10 Jul, 2022 1 commit
  3. 15 May, 2022 1 commit
  4. 05 Apr, 2022 3 commits
    • Greg A. Woods's avatar
      include actual screen resolution in the resX & resY menus · d92f14a7
      Greg A. Woods authored and Alan Coopersmith's avatar Alan Coopersmith committed
      
      
      When given the "-scaled" option fetch the actual screen resolution and
      add that to the list of available resolutions for the resX and resY
      menus.
      
      I.e. If the pattern contains '*' for the resX and resY fields (i.e.
      instead of '0') then we wil end up with the menu containing "0, 100,
      NNN", which makes for a really good demonstration of how scaling of
      fonts without knowing the true screen resolution can lead to very wonky
      results.  Even if the values in the pattern are '0' you still get the
      true DPI as an option in the menus.
      
      When you specify a size for a scalable font, you should use points,
      never pixels.  Points are a physical unit of measurement.  There are
      always 72 points per inch.  Never more or less.  So to scale fonts
      properly on a screen the scaler needs to know the resolution of the
      display in pixels per inch in order to render text at a measurable
      physical point size.  In the current X11 world it is still up to the
      user to correctly specify the actual screen resolution when requesting a
      scalable font to render text with, and this is now possible to
      demonstrate with this change to Xfontsel.
      
      So with the actual correct resolution selected from the resX and resY
      menus (and if the resolution figures are accurate and if the display
      hasn't been scaled by the hardware or, e.g. XrandR) then choosing any
      avaliable point size will show the sample text with a height on the
      screen physically matching the chosen point size.  To that end the
      default pixelSizeList resource has been changed to just "0", as it
      should never be changed, and instead the default "pointSizeList"
      resource has been extended with a list of reasonable real-world
      sample (deci)point sizes.
      
      [also touch up the help text and call exit() to exit main()]
      Signed-off-by: default avatarGreg A. Woods <woods@robohack.ca>
      d92f14a7
    • AG's avatar
      Add 'reset' button · 148a592b
      AG authored and Alan Coopersmith's avatar Alan Coopersmith committed
      
      
      It's very tedious to deselect multiple XLFD field names if you want to
      start from scratch (it's often easier to relaunch the app). Hence, a
      simple reset button can be handy.
      Signed-off-by: Alan Coopersmith's avatarAlan Coopersmith <alan.coopersmith@oracle.com>
      148a592b
    • ThomasKuehne's avatar
      Fixed -Wmissing-field-initializers warning · d55f7ed9
      ThomasKuehne authored and Alan Coopersmith's avatar Alan Coopersmith committed
      
      Signed-off-by: Alan Coopersmith's avatarAlan Coopersmith <alan.coopersmith@oracle.com>
      d55f7ed9
  5. 03 Apr, 2022 4 commits
  6. 02 Apr, 2022 1 commit
  7. 06 Dec, 2021 2 commits
  8. 22 Nov, 2018 1 commit
  9. 17 Nov, 2018 1 commit
  10. 10 Mar, 2018 1 commit
  11. 26 Jan, 2017 3 commits
  12. 28 Sep, 2015 1 commit
  13. 03 Jun, 2014 3 commits
  14. 06 Jul, 2013 2 commits
  15. 18 May, 2013 1 commit
  16. 25 Jan, 2013 1 commit
  17. 20 Jan, 2013 2 commits
  18. 27 May, 2012 1 commit
  19. 14 Apr, 2012 1 commit
  20. 23 Mar, 2012 1 commit
  21. 29 Sep, 2011 4 commits
  22. 19 Jan, 2011 1 commit
  23. 13 Jan, 2011 2 commits
  24. 12 Jan, 2011 1 commit