On 2025-09-24 05:36, J. Landman Gay via use-livecode wrote:
Actually, maybe the resource fork isn't the problem. What are the usual reasons a stack isn't a stack?
So I don't think the engine has ever looked at the resource fork of hypercard stacks when it tries to load them...
The only reason a stack isn't considered a stack is if the engine can't load it - i.e. there's an error while parsing the binary data.
Its possible the stack has been compressed with Stuff-It or similar (which was quite common as doing so allowed the resource fork to be preserved alongside the data fork, but without the resulting file having a resource fork) - if that is the case here then that would be why the engine doesn't like it.
If you send the stack to support we can take a quick look :) Warmest Regards, Mark. -- Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ LiveCode: Build Amazing Things _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
