Re: [Rosegarden-devel] Crash using velocity property (and volume)event rulers

[D. M. M. <ros...@gm...>]

On Wednesday 12 November 2008, Henrik Andersson wrote:

> 1)
> I agree, its easier to catch which velocity reflecting which note.

There is some inconsistency with respect to selections too, if this is all 
going to work smoothly.  Like if I have a selection and then I open a ruler, 
the existing selection isn't reflected on the ruler.  I probably noticed one 
or two other similar circumstances yesterday, but unfortunately forgot to 
write them down.

Just fine tuning stuff though that's hopefully a simple matter to tweak.

> 2)
> Can you describe those drawingartifacts ? I just added a small patch for
> correcting the Z value so that those lines wont be drawn above a bar
> which
> occured when you rasied a velocity bar value above ~110

That sounds like the source of the artifacts I'm seeing.

> and a redraw of event is done (call to EventSelection.contains()) while
> an addEvent() to the eventselection is done this occurs.
> I have some ideas to get around this problem and will soon provide a
> fix.

OK, great!  All of this looks to be a huge improvement in usability.

I wonder if we want to keep the color representing value idea intact somehow.  
I think the reason Guillaume went with the almost invisible thin red outlines 
for the rulers' native selection display was probably to preserve the color 
of the bars themselves.  I like "blue means selected" just fine, but I have 
the idea maybe we could vary the blue with the height of the bar in some 
mathematically convenient way.  I wonder if it's worth playing with that 
idea.  On the one hand, I do feel like something subtle is missing from this, 
but on the other, it could be a lot of tinkering just to wind up with 
something that looks ridiculous, to serve no really worthwhile purpose.

Hrm.

I'll just throw the thought out then.  That was by no means an official 
mandate.
-- 
D. Michael McIntyre