-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not Saving Stacks #118
Comments
Hi @everythingability, glad you had a successful run. As far as building information, you can find it here. It appears to be a bug with the default stack. A workaround until it is fixed, is to do a "Save Stack As..." and then reopen the stack when you launch again. There is currently no concept of a Home stack or even a default stack. It will always open the default in-memory stack. @defano has done an amazing work, indeed! Hope this helps, |
@ooper-zz When I mentioned the build instructions, what I meant was at no point does it say... type...
I've only got glancing experience of Java (coding in Processing) so I had to Google how to get it running... I did but many might not. You've probably woken a few nostalgic old farts like me who haven't used Gradle :-) One of the best/weirdest features of HyperCard that you never had to save anything. Any chance of that? Maybe as an option - but it really was an amazing feature. |
I see. Glad to see you figured it out. As for the auto-save, I agree. Saving a stack was one of the features that made Hypercard stand out from the crowd, albeit not your standard document-based applications. We can technically do it in Java, as there are plenty of time-tested options for caching, but I will let @defano chime in on his take from a roadmap and priority perspective. |
Hi,
I may have done this wrong. On a 12.3.1 mac and launched WyldCard with gradle run. <- There are no instructions on how to actually build.
One it was running, all was amazing, and although it looked like I could save, it didn't, and wouldn't quit.
Amazing work btw!
The text was updated successfully, but these errors were encountered: