It has been asked:
How do you folks handle designing menubars for both Mac and Windows?
I would consider First doing the normal (*nix) style small window housing the
menus as a windoid or pallate holds ones tools.
create this a a stack that has functions for MenuInit, MenuEnable ,
MenuDisable, MenuTerm. The menu contents and the signals they generate can be
stored in fields or better yet files.
Then if Mac and Win32 versions are needed have the startup() function determine
which Os is present, in stead of opening the MenuStack in new window just use
it, and augment the functions to be mac and win32 aware. This way most of your
code is never aware of HOW anything is displayed but you can be sure that it is,
and in a manner the user is expecting.
downside: lot o' work.
upside: can be very modular and reusable.
not so much work nexttime.
that is a very truthless answer, i prefer using navigation buttons, because i
generaly develope for a touchscreen environment and menus dont work so well.
but it seems like a good solution one i would enjoy working on so long as i
dont have to touch the Windex machine..
-
Robin-David Hammond
KPL
25-8D Van Zant
Norwalk CONN USA
Gerrold's Laws of Infernal Dynamics:
(1) An object in motion will always be headed in the wrong
direction.
(2) An object at rest will always be in the wrong place.
(3) The energy required to change either one of these states
will always be more than you wish to expend, but never so
much as to make the task totally impossible.
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
