Am 29.11.2011 01:39, schrieb Tim E. Real:
> Just a note.
> I'm taking a hard look at configuration saving/loading now.
> Please Let me know if you are doing any work in this area.
i'm not touching this area currently. but i previously changed this a
bit with the following intentions:
* TopWin in cobject.cpp alone manages storing and restoring window
state, window configuration, toolbar states for MDI-fied and
un-MDI-fied windows. the derivatives of TopWin look for a tag
"topwin" in readStatus/readConfig and then call
TopWin::readStatus/readConfig. a derivative's writeStuff calls
TopWin::writeStuff (and writes its own data of course as well)
* this removed all special treatment of some topwins. please don't
introduce new special treatments of topwins. (this makes it hard
to understand "why does the pianoroll save its state but not the
* some (but not all :/ ) derivatives of TopWin used QSettings for
storing window state etc. i removed this as it's done by
* there was the problem that parts of global configuration was
stored in the songfile and when loading, it has overwritten my
"actual" global config. that is, when i load a song robert sent
me, my config gets messed up, as some (but not all :/ ) settings
are overwritten with robert's.
* i fixed that by adding that bool to readConfiguration. we've had
this recently, you know?
* i added a default config file which gets placed into the muse
directory on the first start, so users can have a sane default for
stuff like toolbar states etc.
o i didn't want to use the default values in the sourcefiles
because a) it's hard to find them as they're spread over
whole muse, and b) it's almost impossible (and very, very
ugly) to hardcode the toolbarstates (imagine that you have
to hardcode for about 8 window classes two toolbarstates and
two windowstates which are just extremely long hex strings...
o this makes it easier for us devs to change the default
configuration. with the above mentioned solution (hardcoding
it all), you'd need to set it up, find the corresponding
string in your local config, find the appropriate location
in the code and copy' n'paste it there. repeat that
8*(2+2)=32 times for all window configs...
feel free to change whatever i did, but please keep my intentions in mind.
> 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. IT sense. And common sense.
> Lmuse-developer mailing list