From: Silvan <dmm...@us...> - 2004-10-24 07:41:33
|
Something has been bugging me for awhile. The default color names suggest uses. The "oboe" color for oboe, &c. While it isn't obligatory to use them for this purpose, I'm the sort of anal retentive little dweeb who gets worked up when I have a trumpet segment colored "synth lead" or "harpsichord" or whatever. I could do up my own colors, but the color editor stuff is buggy, isn't at the top of anybody else's list, and is too complicated for me to figure out how to fix. It works best if you leave it alone and just accept the defaults. So I was thinking why not just make the default colors take names for the colors themselves, like in Open Office. red 1, red 2, red 3, &c. While I'm at it, since we haven't and aren't soon going to do anything about my RFE about segment preview colors being XORed against the segment color, I'd like to fiddle with the defaults to remove the most pastel colors that leave the segment previews impossible to see. Just trying to keep things looking as good as possible out of the box. It's a UI change after a fashion, but I think it would look better overall. Maybe do eight shades of all the usual colors or something very like Open Office's default palette. Of course, color is a very subjective thing. If somebody active loves this the way it is, I can be talked out of these notions pretty easily. If they were set up by the color patch guy who abandoned us ages ago, and hasn't answered any of the mail I sent him, then I say let's change it. -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ |
From: Richard B. <ric...@fe...> - 2004-10-24 14:23:26
|
On Sunday 24 October 2004 07:18, Silvan wrote: > So I was thinking why not just make the default colors take names for the > colors themselves, like in Open Office. red 1, red 2, red 3, &c. Yeah, well I wanted this in the first place too - but Mark (Hymers - still here?) argued against that quite vehemently I seem to remember at the time. And as he coded it I demurred. Mind you, I did have to drop in a "hidden" colour map for the user of controllers otherwise sharing colours across application functions makes no sense. I think a shake down is probably in order but not until after 1.0 of course. R |
From: Mark H. <ma...@hy...> - 2004-10-29 00:03:46
|
On Sun, 24, Oct, 2004 at 03:23:21PM +0100, Richard Bown spoke thus.. > On Sunday 24 October 2004 07:18, Silvan wrote: > > > So I was thinking why not just make the default colors take names for the > > colors themselves, like in Open Office. red 1, red 2, red 3, &c. > > Yeah, well I wanted this in the first place too - but Mark (Hymers - still > here?) argued against that quite vehemently I seem to remember at the time. > And as he coded it I demurred. Mind you, I did have to drop in a "hidden" > colour map for the user of controllers otherwise sharing colours across > application functions makes no sense. I think a shake down is probably in > order but not until after 1.0 of course. I'm still lurking... I didn't think that just putting the colour names in was particularly useful in a musical context and tried to group colours by instrument type to make it easier to work with initially. The idea is that you can see where you have different sections of the orchestra/band/whateveryoucallit doing what. I realise this is probably more applicable to 'classical' type composition than 'modern' type stuff. If that's bollocks then I can always run up a quick patch to change the defaults to simple colour names :-) Hopefully I'll get around to some proper coding again at some point... Mark -- Mark Hymers <mark at hymers dot org dot uk> "Everyone is entitled to be stupid but some abuse the privilege." Unknown |
From: Mark H. <ma...@hy...> - 2004-10-29 00:05:17
|
On Sun, 24, Oct, 2004 at 02:18:08AM -0400, Silvan spoke thus.. > Of course, color is a very subjective thing. If somebody active loves this > the way it is, I can be talked out of these notions pretty easily. If they > were set up by the color patch guy who abandoned us ages ago, and hasn't > answered any of the mail I sent him, then I say let's change it. Err.. I haven't recieved any email! When did you send it (it might have got lost somewhere at my end...). Mark -- Mark Hymers <mark at hymers dot org dot uk> "Everyone is entitled to be stupid but some abuse the privilege." Unknown |
From: Silvan <dmm...@us...> - 2004-10-29 01:22:20
|
On Thursday 28 October 2004 08:06 pm, Mark Hymers wrote: > On Sun, 24, Oct, 2004 at 02:18:08AM -0400, Silvan spoke thus.. > > > Of course, color is a very subjective thing. If somebody active loves > > this the way it is, I can be talked out of these notions pretty easily. > > If they were set up by the color patch guy who abandoned us ages ago, and > > hasn't answered any of the mail I sent him, then I say let's change it. > > Err.. I haven't recieved any email! When did you send it (it might have > got lost somewhere at my end...). Must have I guess. It's been a bit. I don't quite remember when, or what for that matter. I'll see if I can dig it back up. I think I still have every message I've ever sent since switching to Linux. My ~/Mail directory is... 225M /home/silvan/Mail That's a lotta plain text! -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ |
From: Silvan <dmm...@us...> - 2004-10-29 01:30:48
|
On Thursday 28 October 2004 08:05 pm, Mark Hymers wrote: > The idea is that you can see where you have different sections of the > orchestra/band/whateveryoucallit doing what. I realise this is probably > more applicable to 'classical' type composition than 'modern' type stuff. > > If that's bollocks then I can always run up a quick patch to change the > defaults to simple colour names :-) Hopefully I'll get around to some > proper coding again at some point... I think it is bollocks, really. I can always tell what's doing what because I can see what the track labels are. It might be different if they stayed stuck to the left margin, and scrolled off, but they're always right there. I find in practice that names like "harpsichord" encourage me to use that color for all the harpsichord parts, and then I'm actually reluctant to use any other color on that track. It seems to defeat the purpose somewhat because I'm inclined to use the color to mark off this is the A part and this is the B part and so forth. Really convenient when arranging bits of recycled this and that into something. Of course nothing is stopping me from creating custom colors, but I still feel pretty strongly that it would be more reasonable just to offer a selection of colors with neutral, generic names. Since you're around, why not take a look at http://sourceforge.net/tracker/?func=detail&aid=1039599&group_id=4932&atid=104932 and see if you can make anything of it. There's some flake here. It seems harmless enough, in that it doesn't actually result in a crash, but I keep winding up with no "stock" colors, and then I go make some, save, reload, and wind up with something like what's attached to that bug, where there are two conflicting ideas about what the colors are. I'm probably never going to actually dig into that, so if you've a mind to poke around, maybe you can offer some insight. -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ |
From: Mark H. <ma...@hy...> - 2004-10-29 14:11:40
|
On Thu, 28, Oct, 2004 at 09:30:38PM -0400, Silvan spoke thus.. > Of course nothing is stopping me from creating custom colors, but I still feel > pretty strongly that it would be more reasonable just to offer a selection of > colors with neutral, generic names. Fair enough. If nobody objects, I'll post a patch to change this soon. (I don't want to just commit having been away for a long time and knowing that you're getting ready for 1.0). > Since you're around, why not take a look at > > http://sourceforge.net/tracker/?func=detail&aid=1039599&group_id=4932&atid=104932 > > and see if you can make anything of it. There's some flake here. It seems > harmless enough, in that it doesn't actually result in a crash, but I keep > winding up with no "stock" colors, and then I go make some, save, reload, and > wind up with something like what's attached to that bug, where there are two > conflicting ideas about what the colors are. > > I'm probably never going to actually dig into that, so if you've a mind to > poke around, maybe you can offer some insight. I'll try and have a look at it this weekend. Mark -- Mark Hymers <mark at hymers dot org dot uk> "I told you I was ill" The epitaph of Spike Milligan (1918-2002) |
From: Silvan <dmm...@us...> - 2004-10-29 17:52:39
|
On Friday 29 October 2004 10:15 am, Mark Hymers wrote: > On Thu, 28, Oct, 2004 at 09:30:38PM -0400, Silvan spoke thus.. > > > Of course nothing is stopping me from creating custom colors, but I still > > feel pretty strongly that it would be more reasonable just to offer a > > selection of colors with neutral, generic names. > > Fair enough. If nobody objects, I'll post a patch to change this soon. > (I don't want to just commit having been away for a long time and > knowing that you're getting ready for 1.0). Did I correctly surmise in my earlier post that this change would only involve fiddling with the stock autoload.rg file? If that is indeed the case, then I wouldn't be too worried about committing the change. If not, what else is involved? You can always post the patch to the list for review if you're worried about breaking something. > > http://sourceforge.net/tracker/?func=detail&aid=1039599&group_id=4932&ati > I'll try and have a look at it this weekend. I'd appreciate that. I realize it's not a very helpful report. I've never been able to figure out how I keep painting myself into that same corner. Something borked somewhere though. -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ |
From: Mark H. <ma...@hy...> - 2004-10-29 19:51:56
|
On Fri, 29, Oct, 2004 at 01:52:25PM -0400, Silvan spoke thus.. > Did I correctly surmise in my earlier post that this change would only involve > fiddling with the stock autoload.rg file? If that is indeed the case, then I > wouldn't be too worried about committing the change. Oh yeah, it's just that. I just don't like disappearing for ages then coming back and committing again without a word! > > I'll try and have a look at it this weekend. > > I'd appreciate that. I realize it's not a very helpful report. I've never > been able to figure out how I keep painting myself into that same corner. > Something borked somewhere though. I'll just have to build CVS and play with colours until I break it I suppose! Mark -- Mark Hymers <mark at hymers dot org dot uk> "I'm so gorgeous, there's a six month waiting list for birds to suddenly appear, every time I am near!" Cat, Red Dwarf Series VIII - Back in the Red |
From: Silvan <dmm...@us...> - 2004-10-30 05:24:48
|
On Friday 29 October 2004 03:56 pm, Mark Hymers wrote: > Oh yeah, it's just that. I just don't like disappearing for ages then > coming back and committing again without a word! Yeah, that's cool. > I'll just have to build CVS and play with colours until I break it I > suppose! Please do. I've done a crap job of figuring out how I got there. It keeps happening when my mind is on something else, and I don't really feel like stepping back to futz around and try to reproduce the trouble in a repeatable way. I'm a terrible bug reporter. I should be fired, but who would they get to... Um... -- Michael McIntyre ---- Silvan <dmm...@us...> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ |