From: Guillaume L. <gla...@te...> - 2001-11-12 00:50:42
|
On Sunday 11 November 2001 20:33, Chris Cannam wrote: > > At the moment when you click on the ruler, the cursor positions > itself at the precise pixel position at which you clicked. Much > more useful would be if the cursor was positioned just at the > start of the nearest event to where you clicked But how do you do that with multiple staves ? > I must say, entirely aside from that, I'm finding the new cursor- > placement method pretty tricky to use -- the ruler just isn't big > enough to click on, Yes. At one point for testing purposes I doubled its height to 20, and it was much easier to deal with but still a bit too big. I'm trying 15, tell me what you think. > and being able to drag the cursor isn't a > great deal of use. We could definitely do with shift-click or > something. Yup. Merely having to move the mouse up to the staff to change its position isn't very practical. > work within the present structure. It has to live somewhere > else, because it needs to know about things like clef and key. > Which also suggests some potential efficiency issues, in > traversing the staff to find out those things. Hmm. How feasible would it be to cache this data ? (clef/key positions) -- Guillaume. http://www.telegraph-road.org |