Just a design decision, based mostly in ease of implementation. From above:
Bike is now using the default OS provided mechanism for saving this (view) state. For whatever reason that system discards state when you close document.
The nice thing about this system is that it’s well know and relatively easy to plug into. Of course the difficult part is that it doesn’t really work the way many people want it to work. I agree that (at least as option) it would nice to not loose this state when closing document.
The issue is it’s a chunk of work to implement.
Ideally I could just reuse the existing state saving system and change a few lines of code to save that state along with the document. I’ve tried this a few times, but haven’t been able to figure it out. TaskPaper is using a different route and it mostly works, but for example notice that if you have a single document with multiple tabs open that state won’t be restored if you close the document… only the folds are restored. On the other hand if you leave the document open and quit/reopen TaskPaper they are restored. Probably not that big a deal, but the reason is because in TaskPaper there is a separate path for both state restoration system, ideally I don’t want to have that.
Anyway I do want to implement this as an option. This thread is pushing it more into the forefront of my mind.