In my experience, it is unfortunately necessary to thoroughly test your program in the three environments (native MacOs8 or 9, Classic under OsX and Osx). Differences exists in :
- menus (specially the first one, as you experiment)
- program icons
- information in the finder "Information" window
- aspects of buttons, scrolling field and palette windows whatever LookAndFeel you choose. For instance, defaut buttons are very nice looking on OsX, but you cannot control several of their properties (colors, for instance).
- some behaviours for pop-up buttons or window activation, applescript ...
and certainly numerous others I have not discovered yet.
Just an example during the first test of the new version of my nutrition shareware : the program closed at launch because "the filename of this stack" does not give (at least apparently) the same result in Classic and OsX.
Regards,
Herve Proudhon
Shari,That would be better than a permanent useless menu hanging out there. Especially one that doesn't even have my program's name.
You could write the code in the startup handler of your app that would
change the value in the Info.pList file, but that would only "take" for
subsequent launches; the first time, the user would see "MetaCard".
I still wonder if it's just another menu btn, why not just insert code to change it or hide it, as I would any other menu btn?
Not planning to upgrade in the near future. Too many of my programs would break :-)
The other way is to ship your standalone to someone with OS X and let them
fix it for you (until you get a copy of OS X of your own).
Ken Ray Sons of Thunder Software-- --Shareware Games for the Mac-- http://www.gypsyware.com _______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard
_______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard
