Interesting bug,
There's an issue in trunk where any text object extends far above and below it's visible bounding box. A serious issue reported to me twice at LGM and frustrating to me doing any sort of text work.
Is this the same or similar issue? Should the selectable area for text be the visual bbox instead?
I'd like to say that spaces in text are not the same as invisible objects which are not the same as no objects. Yet if I understand KK's post on the bug, they should be treated the same way.
My opinion is that spaces in text are visual objects that are visible, even if they are unapparent. As much as 0.1% opacity rectangle is still "visible" anyway.
Make all objects selectable and make the ability to select behind objects easier. Make it easier to deal with transparent objects.
Martin
On Fri, 2014-04-11 at 11:35 -0700, mathog wrote:
In this bug:
https://bugs.launchpad.net/inkscape/+bug/1243401
there is a discussion about whether or not the selectable area for a text object should include leading and trailing spaces. That is, for text objects 1 = " " and 2 = " a b " the old behavior was that the "arrow" or "+A" selection pointers would not detect object 1 at all and would move across the leading and trailing spaces of object 2 without registering a hit. The patch in that bug makes these pointers treat spaces like any other character.
People were coming down on both sides of the change and ScislaC suggested moving that discussion here. See posts 20-27 for the discussion so far.
Regards,
David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech
Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel