Re: NSString and gdb
Re: NSString and gdb
- Subject: Re: NSString and gdb
- From: Kim Foo-Jones <email@hidden>
- Date: Sun, 25 Nov 2001 22:56:58 +0000
In all three cases, you could choose a smaller font for the
text at a lower screen resolution to get the same result.
I use Monaco 9pt for code editing, and you can't really go lower
without it becoming unreadable, whatever the resolution.
Also, if you lower the resolution you get ridiculously big menu
bars and title bars (particularly with OS X). I'm using a 19"
monitor at 1600x1200 and I'd like to go higher, but I can't
convince the Displays preferences to let me (at a sensible
refresh rate. My monitor (Sony G240) claims to be able to do
1920x1440, but that's not given as an option.)
The only time I have problems with this setup is when receiving
email from people (usually Windows users, since font sizes are
different there) who set the font size to 10 pt Arial, which is
tricky to read. Then it's a simple matter of using Mail's
"Bigger" option...
Bigger fonts with higher resolution just give a slightly
smoother character display at the cost of processor cycles and
need of additional memory (4 bytes per window pixel). Roughly
20% Graphics performance loss for each 10% of size increase
(e.g. 10px to 11px).
Are you sure? Switching down to 1024x768 doesn't make it seem
that much faster... And the smoother display is well worth the
Hmm - I'm sure, a lower resolution won't harm.
Pixels also start looking blocky and fuzzy at lower resolutions
on larger monitors.
Beyond 80 dpi, you don't get much anymore on CRT Displays.
I beg to differ... I love my 116ish dpi! Setting the zoom to
160% in a word processor gives me very smooth WYSIWYG.
But anyway, this is all a bit off-topic. If anyone has any
further points to make, please feel free to mail me off-list.
-Kim