From: Tim E. R. <ter...@ro...> - 2011-09-16 01:29:38
|
On September 15, 2011 12:23:39 am Orcan Ogetbil wrote: > On Sun, Sep 11, 2011 at 12:43 PM, Tim E. Real wrote: > > On September 11, 2011 02:54:59 am you wrote: > >> By the way, is the green and the red in the automation button on the > >> bottom of the audio strip (use mouse wheel over the automation button) > >> too bright? Do we need them more pastel? > > > > Yeah pretty glaring, also the strip labels. > > As I said I applied a gradient to them only to realize they looked stupid > > against all the other non-gradient controls. Sigh, no style sheet. > > But really that was only because when automation is 'off', the colour is > > grey, and it didn't look right against the other non-gradient grey > > controls. Perhaps I can change that to some other shade or something. > > Or as you say, no gradient but more pastel-ish. Yeah that might work! > > The gradient code is still in there, commented out. > > I changed the default colors of the track labels (also of the bigtime > foreground, transport handles, arranger track backgrounds) to more > pastel colors. > > Also in the arranger, I made it so that the selected track is shown in > a gradient instead of in some green color. > > Feel free to yell about these changes. They are a little experimental > right now. I want to tune them into everyone's liking (well, if that's > ever possible). > > About namespaces... I want to make MusEMidi and MusEAudio namespaces. > Is this a reasonable cut? Why? Are there exposed global variables? If not don't bother. > What is the best thing to do with the Mess > stuff and the related plugins then? Nothing! Don't do them. They are limited to what they expose by the __attribute__ ((visibility("default"))) in the MESS descriptor, and by COMPILE_FLAGS "-fvisibility=hidden". As the comments say, the only visible symbol is "mess_descriptor". Tim. > > Orcan |