Marcus Jacob <rossi@xxxxxxxxxxxxxxx> wrote: > Hi Clemens, > > honestly, I don't get your problem. With the > revised patch, just the position is restored > unless you take extra measures. I'm with Clemens here, for two reasons: simple behavior and simple code. 1. A simple, easy to understand and predictable "rememeber-position-and-state"-behavior which most applications can abide by, is good for usability. I think the following rules meet the above criteria: - remember one window position, the last one closed - tile when opening multiple - never force a workspace switch on the user This is common BeOS application behaviour, FWIW. Maybe there are a few sets of good behaviour - for different kinds of applications - to identify and standardize on. 2. The source gets cluttered up by (possibly) less frequently used optional behavior, the boiler plate parts of Haiku's application diverge somewhat and third party developers might overlook the simple implementations and go for more convoluted ones, if Haiku fails to lead by example. Just my two Pfennig. /Jonas.