Hi,
So in theory Decker shouldn't crash, even if you write something that doesn't work. And the things not saving sounds like an issue. In the interests of figuring this out so it can be fixed for others, can you let me know what you'd put into Dialogizer that crashed things, so I can try and see if I can recreate it? And also, what sort of things weren't saving?
Also, just want to mention this was a really lovely project that turned out really well, great work!!!
Oh, that's weird then. Hm. Luckily, I had saved a old build where I had kept that broken code. So, in the field property that I used as a "source" for my dialogue I had !go["Next" "SlideLeft"] . And when I playtest it, clicking the widget that suppose to start the dialogue, whenever it got to that function, it will actually do the function but the program just cuts off before it reaches its full completion.
And abt the saving, it missed like little things here and there like if I had changed a word on widget or moved it elsewhere on the screen. (What's funny is that I just checked my current build, and I see that it didn't save one word I change in the final build I had up, haha. Pretty sure, I had the autosave on.)
Let me know if I should send you the old build itself or anything to help fix this! And thank you so much for the kind words, I'm glad you enjoyed the final product <33
So, when you quit Decker it pops up the thing about saving your changes, had you been clicking "save" on that? My understanding is Autosave runs periodically (like every however many minutes) so it may be missing the final changes if you make them right before finishing
Edit: I've been told that when autosave is on it will just save automatically so I'm guessing you're not seeing the prompt haha
Millie helped me track down the source of your reported crash. A fix is included in Decker 1.60.
