« Return to Thread: Re: [Rosegarden-bugs] SF.net SVN: rosegarden:[10457] trunk/rosegarden
Re: [Rosegarden-bugs] SF.net SVN: rosegarden:[10457] trunk/rosegarden
by D. Michael McIntyre-3
::
Rate this Message:
On Thursday 02 July 2009, you wrote:
> I know alignment and the behaviour with the panner is quite a way off
> right now. What were the other significant caveats you noticed?
Alignment didn't actually jump out at me, so I did some serious looking. I do
see alignment problems now, and the alignment is arguably worse than before.
Alignment has never been perfect though. If we assume that the position of
the event rectangle on the canvas represents the correct starting and ending
points A and B, respectively, which the ruler bar should mirror, then I find:
Default zoom
Classic velocity bar starts at: A + 2 or A + 3 (seems random)
ends at: B
Thorn velocity bar starts at: A - 4
ends at: B - 1
(Thorn metrics off by a margin of error of one pixel in either direction due
to half pixeling, even at default zoom level.)
The starting significantly soon and ending a little early pattern holds out to
the highest zoom level. It's harder to quantify all of this when zooming
out, because of half pixeling and general fuzziness everywhere. (And with no
feedback as to what level of zoom the panner is sitting at, it is hard to
reproduce anything but the extreme stops and the default middle setting
anyway.)
OK, moving past that one, the first thing I noticed yesterday was I entered
some random string of events, and only one of them showed up on the ruler. I
can't figure out how to reproduce that today. Everything I try is showing
up, even when closing out the view and opening another.
Other issues:
* no updates when velocity of existing events changes (eg. using the velocity
tool)
* no color man, or colour if you insist, but either way we must have colo(u)r!
(I can probably take a moment to go add that back in if you'd like.)
It's a pretty short list, really. The alignment thing took the most effort to
really look at precisely and quantify, and it's actually the thing that least
stood out to my eye. The alignment on the rulers has always been out of
whack anyway, you see. Yours is just out of whack in a different way,
missing the mark at both target points instead of only one of them.
--
D. Michael McIntyre
------------------------------------------------------------------------------
_______________________________________________
Rosegarden-devel mailing list
Rosegarden-devel@... - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
> I know alignment and the behaviour with the panner is quite a way off
> right now. What were the other significant caveats you noticed?
Alignment didn't actually jump out at me, so I did some serious looking. I do
see alignment problems now, and the alignment is arguably worse than before.
Alignment has never been perfect though. If we assume that the position of
the event rectangle on the canvas represents the correct starting and ending
points A and B, respectively, which the ruler bar should mirror, then I find:
Default zoom
Classic velocity bar starts at: A + 2 or A + 3 (seems random)
ends at: B
Thorn velocity bar starts at: A - 4
ends at: B - 1
(Thorn metrics off by a margin of error of one pixel in either direction due
to half pixeling, even at default zoom level.)
The starting significantly soon and ending a little early pattern holds out to
the highest zoom level. It's harder to quantify all of this when zooming
out, because of half pixeling and general fuzziness everywhere. (And with no
feedback as to what level of zoom the panner is sitting at, it is hard to
reproduce anything but the extreme stops and the default middle setting
anyway.)
OK, moving past that one, the first thing I noticed yesterday was I entered
some random string of events, and only one of them showed up on the ruler. I
can't figure out how to reproduce that today. Everything I try is showing
up, even when closing out the view and opening another.
Other issues:
* no updates when velocity of existing events changes (eg. using the velocity
tool)
* no color man, or colour if you insist, but either way we must have colo(u)r!
(I can probably take a moment to go add that back in if you'd like.)
It's a pretty short list, really. The alignment thing took the most effort to
really look at precisely and quantify, and it's actually the thing that least
stood out to my eye. The alignment on the rulers has always been out of
whack anyway, you see. Yours is just out of whack in a different way,
missing the mark at both target points instead of only one of them.
--
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: Re: [Rosegarden-bugs] SF.net SVN: rosegarden:[10457] trunk/rosegarden
| Free embeddable forum powered by Nabble | Forum Help |
