Chris wrote: >> You have to be careful to double-click outside the "capture zone" >> that exists around each note and each rest, don't you, otherwise a >> window with an extremely long detailed list of object properties >> appears? The capture zone around tied chorded notes seems to be >> quite huge as if it were the least enclosing rectangle around the >> tied chorded notes and their stems, so I found I had to double-click >> a very large distance from any notes or rests to be absolutely sure >> of not getting the properties window unexpectedly. > >Unfortunately the technical reason for this is a fairly fundamental >one -- there is a single rectangular object on the canvas that >contains the rendering of all the above parts of the chord, and at >a very basic level your click is determined to have collided with >that object: we don't even decide what to do with your click until >after the toolkit has already made that decision.
It'd be a great pity if that architecture totally prevented the implementation of any way of reducing the effective size of the capture zone. It's counter-intuitive and quite counter-productive too when you're trying to work as quickly as possible on a composition. The rectangular object for each set of tied chorded notes doesn't have any lower-level objects, rectangular or otherwise, on the canvas to describe the components? If it did, couldn't RG trap events on the union of those smaller objects, which would be smaller than the least enclosing rectangle? William ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
