Sooo, I think I just got bitten by the issue Andrew talked about the other
week. I tried to set default parameters but they never appeared since
MusE.cfg is sliently replaced by a master copy upon startup, if it does not
already exist.
I guess this is a question, pros, cons of having this file?
What it basically means is that the configuration set in gconfig.cpp is no
longer valid it just defines placeholders for the datatypes.
Actually it shouldn't be needed at all, I tried now commenting it out
completely and it seem ok apart from some parameters I guess aren't set in
the default MusE.cfg.
Unless there is a good reason may I propose that we remove the config in
gconfig.cpp and instead keep the default MusE.cfg updated?
Doing the opposite, removing this file and going back to default config in
code is of course also possible, I do dislike having a foot in both
solutions though.
Thoughts?
/Robert
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
