That's it :) The Tremulant and Coupler buttons all have Custom Palettes.
Resetting them to Inherited cures the problem, but now another has emerged regarding the whole UI. The default "button pressed" colour is not sufficiently different from the "button not pressed" colour to show which stops are on and which are not. Which colour do I need to edit in the palette to make an overall change to the button background when the button is "pressed"? My empirical attempts are not working :( lasconic wrote > Check mscore/stafftext.ui, Aeolus tab and the palette for these buttons. > Check the palette for the other buttons too. > If you change this file, don't forget to go back to the first tab before > saving it. > > lasconic > > > 2013/9/13 ChurchOrganist < > [email protected] > > > >> Can anyone point me to the code which controls the button colours in the >> Aeolus stops section of the Staff Text Properties UI? >> >> Most of the buttons are conforming to the defaults set in MuseScore.cpp >> at >> lines 4744ff but the coupler and Tremulant buttons are stubbornly >> remaining >> brown and green respectively, with consequent effects on their button >> text >> readability. >> >> >> >> ----- >> Regards >> Michael >> -- ----- Regards Michael -- View this message in context: http://dev-list.musescore.org/Staff-Text-Properties-UI-tp7578330p7578332.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk _______________________________________________ Mscore-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mscore-developer
