search

atg / chocolat-public

Public bug tracker for the private chocolat project
http://chocolatapp.com
182 stars 4 forks source link

Chocolat doesn't remember window position #1779

Open yellow-pumpkin opened 8 years ago

yellow-pumpkin commented 8 years ago

Yes, I consider this a bug. Especially for an app that advertises itself als "native" for Mac. I know some people don't care about this, but I do. I hate Chocolat because of this. It would be perfect, but this is a deal breaker. Seriously, every single app I use saves the window position, so what gives? I've been using Chocolat for years now, and this is just so annoying.

locks commented 8 years ago

It remembers and works properly for me, so I can't reproduce this.

yellow-pumpkin commented 8 years ago

Well, then it's a bug. When I cmd+N for a new file (opens a new window), and then I quit the app and open it up again, the window is positioned where the last (cmd+N) window was. But when I drag the window around myself, quit and then open the app again, the window isn't where I last dragged it at. So no, it doesn't remember.

atg commented 8 years ago

Chocolat tries to be a native text editor, but Cocoa does not natively support having multiple documents sharing one window. Everything to do with window management is necessarily a hack!

What would you consider "perfect" window management?

atg commented 8 years ago

At the risk of possibly rationalising a bug, I think the reasoning for the current behaviour is that window size is a preference, but window position is not (necessarily). When I move a window, it's often to make room for some other window that will be gone the next time I launch Chocolat. When I resize a window I'm making a statement of how much screen area I want it to take up.

yellow-pumpkin commented 8 years ago

I understand what you are saying, and if it's too much of a hassle to change the current behavior, that's fine. What I really don't like however is that the window sometimes does change position after a restart (namely when cmd+N for a new file/window, this position is saved as the new one). I don't see any logic behind that, it's confusing. It makes no sense (from a usability perspective) that the window position isn't saved when the user drags it somewhere, yet it is saved when the user uses cmd+N for a new window (which always opens a few pixels under the current one, as you know). I don't know if that's intentional or not, but in the current state, the position is just "jumping around" in the eye of the user. Of course the user remembers where he last dragged the window, but not where the last window popped up when he used cmd+N (as he likely dragged it somewhere else afterwards). So either don't save the position, at all, or do save it (including when the user drags it somewhere). I would be fine with the window always opening up in the center for example. That's a trade-off I would gladly make. Just to have a sense of "control". Because right now it feels I don't.