« Return to Thread: Ruler comments
Ruler comments
by D. Michael McIntyre-3
::
Rate this Message:
On Thursday 02 July 2009, cjnfryer@... wrote:
> Log Message:
> -----------
> Fixed MatrixVelocity bug so velocity no longer drops to zero below a
> certain point.
This change made a very big difference in behavior, and the results are much
better now. The only lingering thing I'd grouse about there is the way a bar
will grow so tall that the top of its border is cut off when it hits the
upper limit.
> Log Message:
> -----------
> Colourful property control ruler.
> I'm using 'lighten' for the colour of items that are not selected.
> This has the effect of moving them towards the white background (should
> really desaturate aswell). I like it and would like to use the same thing
> in the matrix.
A few of the velocities I picked at random, the colors didn't lighten so well.
At a certain range, you're getting into dark yellows that become bright
yellows, and then revert back to dark yellows when unselected. It looks a
bit strange. A good idea, just with a bit more tweaking indicated I think.
Also, we really need some kind of alpha in here too, as a way to help deal
with overlapping velocities. A chord with a different velocity in each note,
the note with the highest velocity obscures everything else. I think the
event rectangles on the matrix grid are already only 80% opaque (I have no
idea what the real figure is) to show up overlapping events more easily. We
could just find wherever that is and apply it in the ruler too.
> By the way, I think we should standardise the spelling of 'colour' to
> 'kuller' because that's easier for those at the back.
I'd almost vote for that after I just worked on a chunk of code with QColor
here, Colour from one of our classes there, and Color from another one of our
classes spread around in the middle. I used Colour in the new code as a nod
to the Chrisses, but a good case could have been made to use Color instead.
Kuller doesn't actually seem like such a ludicrous idea, but only if we can
have QKuller too.
(As far as that goes though, in the 18th century we changed "colour"
into "color" and you changed "curb" into "kerb." At least "color"
and "colour" are mutually intelligible. I had to encounter "kerb" about ten
times before I realized it was a real word with a long history, and not some
cute online gamer spelling like "teh" or "moar.")
--
D. Michael McIntyre
------------------------------------------------------------------------------
_______________________________________________
Rosegarden-devel mailing list
Rosegarden-devel@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
> Log Message:
> -----------
> Fixed MatrixVelocity bug so velocity no longer drops to zero below a
> certain point.
This change made a very big difference in behavior, and the results are much
better now. The only lingering thing I'd grouse about there is the way a bar
will grow so tall that the top of its border is cut off when it hits the
upper limit.
> Log Message:
> -----------
> Colourful property control ruler.
> I'm using 'lighten' for the colour of items that are not selected.
> This has the effect of moving them towards the white background (should
> really desaturate aswell). I like it and would like to use the same thing
> in the matrix.
A few of the velocities I picked at random, the colors didn't lighten so well.
At a certain range, you're getting into dark yellows that become bright
yellows, and then revert back to dark yellows when unselected. It looks a
bit strange. A good idea, just with a bit more tweaking indicated I think.
Also, we really need some kind of alpha in here too, as a way to help deal
with overlapping velocities. A chord with a different velocity in each note,
the note with the highest velocity obscures everything else. I think the
event rectangles on the matrix grid are already only 80% opaque (I have no
idea what the real figure is) to show up overlapping events more easily. We
could just find wherever that is and apply it in the ruler too.
> By the way, I think we should standardise the spelling of 'colour' to
> 'kuller' because that's easier for those at the back.
I'd almost vote for that after I just worked on a chunk of code with QColor
here, Colour from one of our classes there, and Color from another one of our
classes spread around in the middle. I used Colour in the new code as a nod
to the Chrisses, but a good case could have been made to use Color instead.
Kuller doesn't actually seem like such a ludicrous idea, but only if we can
have QKuller too.
(As far as that goes though, in the 18th century we changed "colour"
into "color" and you changed "curb" into "kerb." At least "color"
and "colour" are mutually intelligible. I had to encounter "kerb" about ten
times before I realized it was a real word with a long history, and not some
cute online gamer spelling like "teh" or "moar.")
--
D. Michael McIntyre
------------------------------------------------------------------------------
_______________________________________________
Rosegarden-devel mailing list
Rosegarden-devel@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
« Return to Thread: Ruler comments
| Free embeddable forum powered by Nabble | Forum Help |
