From: Tim E. R. <ter...@ro...> - 2011-09-29 22:11:54
|
> Am 29.09.2011 06:38, schrieb Tim E. Real: > >> What has happened to configuration? > >> > >> It hardly remembers anything now. > >> > >> It won't remember main window and/or arranger size, > >> and it won't remember mixer size and/or position. > >> > > Correction - just mixers and arranger, but I think you said you > > were working on the arranger. > > > > > not currently, but i have it on my list. > > first: both are unrelated. i dunno why the mixer isn't stored, but i > know that i made some (actually noncritical??) changes on storing the mixer. > > for the arranger, try the following: > change the arranger's toolbars. then open another topwin (that is: > midieditor, cliplist or master editor), switch to it, switch back again, > then close and restart muse and look if it works now. if not, try the > same thing, but be sure that the "other window" is MDIfied. then switch > from arranger to that one and back, restart and see. > it should work then. the problem is, that states are saved when a window > loses focus. closing muse however is faster than receiving a "lose > focus" event, so config isn't stored again. > > >> It won't remember toolbar positions. > >> > > Oops. Erased current configuration, seems to work now. > > Crud. My mistake. > > > strange, though. should we try to add some function for "cleaning" old > configs? or should we simply say "this is a whole new release, there may > be and are some minor incompatibilities"? i favor the first. > > > >> And, what is a configuration file doing in the templates folder? > >> I remember some brief discussion about this but it went by > >> quickly so I missed it. > >> There should be no such files in templates! > >> > well, i thought of it as a "configuration template", so i put it into > templates. OK. But try to move it into its own folder. Template folder is reserved for song templates only. Tim. > >> If you need this, please move it to another folder, such as > >> 'configs' or something. > >> > > Uh, yeah. > > > >> I don't know why this config was moved out of the code. > >> > > To keep it in a file, right? Cool. > > > it makes us developers the life easier. most config stuff CAN be > initalized inside the code, but for some stuff it's really hard or > impossible to do so. the window toolbar states and/or configurations are > such stuff. > of course, we _could_ add some "init win configs" function, which > initalizes all that with hardcoded states. but it's pretty hard to get > to these states; we had to open the config file in a text editor and > then copy about 20 or 30 very long strings into our code. it's more > convenient that way. > also, with the template config file, we can change the default > configuration graphically, and can be sure that there are only valid > combinations of options. i dunno if muse has them, but some programs > have config options which exclude each other. when initing them in the > code, and then changing the initial values without taking enough care, > we possibly could turn two excluding options on, resulting in undefined > or undesired behaviour. that way, this is almost impossible. > > > >> --- > >> Also, there's a slight problem with the dark grey > >> main window background being assigned to the > >> arranger background - until you move the arranger > >> out of the main window. With certain themes. > >> That dark grey arranger background causes problems > >> for example with the track info (redone-) meters' corners being > >> filled with the wrong colour. Not to mention the dark grey just > >> doesn't look right. > >> > > Ah, weird it's actually transparent. With two windows open inside > > the main window, I can see each other through their backgrounds. > > It only happens with certain themes like Skulpture. > > Soon as I move them out, it's fixed, and when moved back in it's > > still fixed - until the theme is switched to Oxygen and then back > > to Skulpture, then all the windows have the see-through background > > again. > > > > > wtf? well, i've probably nothing to do with that, nor do i understand > what's going on there. i think this is up to somebody of you to solve ;) > >> I'm taking a look, hopefully something simple. > >> > > > >> --- > >> Also, the MDI settings in the Global Settings window don't seem > >> to have much effect now. Nothing changes. > >> > > Ugh, I forgot how it works! I think it's OK. > > > i also think so ;) > when you change the mode while windows are open, this does NOT affect > already-open windows. only newly created windows. restarting muse, or > manually putting these windows where you want them helps. > >> At first when I unselected WindowConfig -> As SubWindow, > >> it kept segfaulting (I can look up again where it happened if you want). > >> It was not until I opened the Global Settings and started to > >> change the MDI settings, that it now does not segfault. > >> > > As above, wiped out current configuration, seems to work OK now. > > > this is a really strange config issue then. maybe we should really put > some hint like "if you used muse2 alpha/beta before, and experience > strange voodoo, deleting your config file may help" > > > greetings > flo > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Lmuse-developer mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > |