Hi. I have a bit of a mystery on my hands. Hope someone can help...
I have an old Carbonized app, meant to work on OS9 and OSX. It's
developed using an old CodeWarrior (8.2, I think). It really is rather
outdated, but it does work quite fine (mostly!)....the app includes a
resource and data fork, has a plist resource (no bundle), icns's and
old icons of various depths, etc. The program works fine on my own
computer with Mac OS 10.5.3. It s****ts the application icon that it
should.
BUT...I can see an oddity, and worse yet, one of my customers can't
even use the app, as it comes up (to her) as a Classic App only with a
"bad" icon (looks kind of like two pages of paper, maybe a set of
crossed pencils in the lower right, and the international NO symbol (a
circle with a diagonal line across it.)
Sometimes when I compile a new version, the icon I end up with when
CodeWarrior creates the new app is, indeed, that "bad" icon. And, if I
do a GetInfo on it, it does show up as a Classic App. But,
interestingly, if I click the app's (bad) icon once, to select it, and
then Duplicate it using the Finder, the duplicated file s****ts the
correct icon, and a Get Info on that file shows (correctly)
Application, not Application (Classic).
Another oddity is that when I double-click the "bad icon" (supposedly
the Classic App), the program runs fine, as a regular Mac OSX app. But,
my customer said that when she (also running 10.5.3) double-clicks the
"bad icon", she gets a message saying "You can't open the application
because the classic environment is no longer sup****ted". So, she's out
ouf luck.
So, the question is really two-fold? Why do I sometimes create an app
with that bad icon (where the Mac presumably thinks it's a Classic
app)? And, why even if the app does s****t the "bad" icon for me, am I
able to run the app properly anyway in OSX, yet this one customer
cannot?
THANKS for any thoughts!
|
