Re: Intel writes creator codes backwards!
Re: Intel writes creator codes backwards!
- Subject: Re: Intel writes creator codes backwards!
- From: Harald E Brandt <email@hidden>
- Date: Wed, 18 Oct 2006 23:59:04 +0200
On 2006-10-18, at 15.40, has wrote:
Harald E Brandt wrote:
Despite I think I have followed the list pretty well, I have not seen
anyone report on the fact that System Events writes both creator codes
and files types BACKWARDS on Intel-based Macs!?
That'll be an endian bug in System Events. File a report (http://bugreport.apple.com).
Also, any particular reason you're using creator/type codes? If you only need to find out what type a file is, see if you can use its uniform type identifier instead - UTIs are better anyway. (See my other recent post.)
I just had a response from John Comiskey at Apple, and he says this is the first time he has heard about it! That amazes me, and that is why I didn't report it formally since I took for granted it was known!
The first time I heard of a customer having a problem was in August 3rd on a MacBook Pro, but it was not until October 16, I got to know that the reason is that the codes were backwards!! I have not formally reported the bug, since I simply couldn't imagine that I would be the first on earth to discover it! (Besides, I do not even own an Intel Mac -- I have sent test scripts to a customer, and the test script sends a mail to me with results, so that is how I know what the problem is.)
The reason I use System Events rather than Finder is because I have trusted it more! For instance, If I drag and drop files to my app, Finder is busy and completely locks the app until the whole thing is over, so I am extremely cautious of calling Finder, and besides, it seems generally slower and have more strange behaviors than System Events, in my view. However, this time, it seems the opposite is true!
The reason for Creator code is:
My software (a Studio app) downloads stock market quotes and generates a file that is imported into the application ProTA (not made by be). The file is regenerated each time and it is basically just a text file. So in principle, if it should get any extension at all, it would be 'txt'. I tell ProTA to open it. So far it's OK. However, I want to be nice, and make it possible for the user to double-click the file to make it automatically open (and imported) into ProTA. That last thing requires a creator code, since a file with 'txt' extension would only open in Text Edit! Or do you have a better suggestion?
Actually, that ProTA has been a Classic app, and for years we have been awaiting an OS X app. My app is OS X, and I made it so that it would work with both the old Classic and the upcoming OS X version of ProTA, since I got the creator code for the upcoming OS X version from the developer of ProTA two years ago. Now there is an OS X beta of ProTA, and my app works fine with that, but only as long as the processor is not Intel!
Just today I got another response from the guy I am sending test scripts to: If I set the codes using Finder, it seems to "sometimes" work!? I can't understand why it is only sometimes!? Perhaps it is a caching issue, when that file of mine gets different creator codes at different times, depending on which test script he is running? What do you think?
______heb____________________________
Harald E Brandt http://bragit.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden