From: Robert J. <spa...@gm...> - 2011-09-15 15:07:11
|
Hi Florian, 2011/9/15 Florian Jung <flo...@we...>: > Hi > > yeah, why are they stored there? > is this a relict of times where the configs weren't stored into muse's > global config file? > is there any sense for this? Need to think about this. Can you give some example on config per window class? (I'll try to take a look later tonight) My thought on our default templates is that they should be edited to not include unnecessary configuration. Maybe there is reason to remove configuration altogether. Regards, Robert > > i'd like to remove it, because it breaks loading settings. whenever you > load a song (including templates!), this partially overwrites your saved > configuration, which really sucks. > > i can understand that window _state_ has to be saved. but > _configuration_ (that is, settings "per-windowclass" and not > "per-window") is useless now. > > can i remove this, or are there reasons for this? if i can NOT remove > it, what would you suggets to circumvent the "templates overwrite > MusE.cfg's configuration settings"? > > greetings > flo > > ------------------------------------------------------------------------------ > Doing More with Less: The Next Generation Virtual Desktop > What are the key obstacles that have prevented many mid-market businesses > from deploying virtual desktops? How do next-generation virtual desktops > provide companies an easier-to-deploy, easier-to-manage and more affordable > virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > |