Yeah, the mistake was on my part (as stated, I didn't think to hit Escape; instead I hit Enter and tried to either use Save or find an exit method that way, but no go, so I resorted to [X]).
What's interesting however is that the game does appear to have knowledge of how many trinkets I have (20), but somewhere else within the save files still thinks I have only 17. So there's an inconsistency that got created, somehow, as a result of closing the application.
I'm speaking strictly about Windows here, but I'm certain there's an equivalent on OS X.
Code-wise, there shouldn't be any functional difference (assuming the programmer implemented a handler for the Win32 WM_CLOSE message correctly) between hitting Escape + choosing "Yes, quit to menu" and pressing [X] (inducing WM_CLOSE). These really should do the same thing. If using the menus does in fact close some file descriptors or do some clean-up work that WM_CLOSE doesn't, then that quite honestly is a bug and can easily be alleviated by ~3 lines of Win32 code (add a case statement entry for WM_CLOSE and have it call the same clean-up and shutdown functions as the menu item). It's important to understand that this isn't the same thing as, say, going into the Task Manager and End Task'ing a process -- that isn't what I did at all.
What's interesting however is that the game does appear to have knowledge of how many trinkets I have (20), but somewhere else within the save files still thinks I have only 17. So there's an inconsistency that got created, somehow, as a result of closing the application.
I'm speaking strictly about Windows here, but I'm certain there's an equivalent on OS X.
Code-wise, there shouldn't be any functional difference (assuming the programmer implemented a handler for the Win32 WM_CLOSE message correctly) between hitting Escape + choosing "Yes, quit to menu" and pressing [X] (inducing WM_CLOSE). These really should do the same thing. If using the menus does in fact close some file descriptors or do some clean-up work that WM_CLOSE doesn't, then that quite honestly is a bug and can easily be alleviated by ~3 lines of Win32 code (add a case statement entry for WM_CLOSE and have it call the same clean-up and shutdown functions as the menu item). It's important to understand that this isn't the same thing as, say, going into the Task Manager and End Task'ing a process -- that isn't what I did at all.