David Fedor wrote:
> // Macros to determine correct character code to use for drawing
> // numeric space and horizontal ellipsis.
> #define ChrNumericSpace(chP) do { /* much stuff */ } while (0)
> #define ChrHorizEllipsis(chP) do { /* much stuff */ } while (0)
Holy macro expansions Batman! :-)
<BORING> <NITPICKY>
Ok, I vaguely recall you telling us at WWDC to just use a 3 dot string
"..." instead of horizEllipsisChr to avoid all this mess. Three months
later, is this still safe on foreign encodings such as Japanese? Or is
the system ellipsis character preferred?
It seems it would work fine (since the '.' char is in the low ASCII
range which is present on all encodings) but maybe three dots are not
appropriate for the local language, if some language had a different
symbol for continuation, for example. (Though I see the Japanese ROM
fonts have the same old '...' ellipsis character.)
Basically at this point my table draw callbacks are well tuned so I
don't want to go back and add a parameter to pass the cached ellipsis
character, nor can I use a global due to Global Find support, and
obviously the new macros are cost-prohibitive for usage inside a table
draw callback.
</NITPICKY> </BORING>
(I'm obsessing about milliseconds here because the guys down the hall
are writing the same application on Windows CE! :-)
-slj-
