[Lmuse-developer] storing toplevel state into templates?

[Florian J. <flo...@we...>]

Hi

i've a question about storing the toplevel state into template files.

muse remembers the initial state of all window classes which derive from 
TopWin, that is in particular, of the arranger window.

this allows you that muse opens the arranger window at the same position 
and with the same size as the last time you left muse. i think that's 
desirable for many people.

however, if a template .med file contains a <toplevel> <arrangerview> 
... tag, this *overwrites* the arranger position read from config, 
effectively making muse NOT remember the arranger state.

but overwriting window settings can be desired, too, especially when 
creating a custom template with, say, one midi track, an arranger window 
AND a piano roll window open.

overwriting them cannot be desired in the templates shipped with muse, 
however!


so what should we do?

    * always manually remove the <toplevel> tag from our templates?
    * offer some checkbox in the save dialog "store window state"
      (defaults to true, we need to manually set it to false whenever
      updating templates)?
    * simply not loading window states when opening a template is not an
      option, as the behaviour might be desired sometimes

i for now removed the <toplevel> tag from the templates, and i'd like 
you to do this as well every time you update the templates.

do you have some sensible answer to it? i don't have really :/

greetings
flo