I sent paul a response, looks like after he posted here. I'll
basically put the same information here as I sent him. I'll update
the website at some point to.
Yes, it is the OSTypes to blame. One of my other users a while back
sent me the trick via e-mail:
"To fix it and make it UB, just change all OSType's to integers, and
convert all OSType strings you're passing to integers as well, and it
works beautifully."
Here's why the release code has not been updated. I don't have an
intel mac yet. I'm not ready to release something into the wild and
call it universal, when I have no way to test it. So, being open
source, you guys may do with it what you like until I get an update
released.
--
Thom McGrath
The ZAZ Studios
<http://www.thezaz.com/> AIM: thezazstudios
On Nov 13, 2006, at 5:07 PM, Charles Yeomans wrote:
On Nov 13, 2006, at 3:30 PM, Joe Ranieri wrote:
The code probably needs to be updated to handle OSTypes correctly
in Intel builds.
Yep, that's exactly the problem. I debugged it for someone a while
back and the OSTypes were being done using a string in a
MemoryBlock so it wasn't respecting the endianness.
Is it not being supported by its developer?
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
