Hi,
From a user POV, lots of people use SVG for scripting (like forms filled by a database, etc. ). For this use, an "empty" (or only containing spaces) text makes sense, as it can be "filled" by a script, and destroying it would not be what th user expects.
Regards, Ed
From: scislac@...400... Date: Fri, 11 Apr 2014 13:18:01 -0700 To: doctormo@...400... CC: inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] Should select area for text objects include leading and trailing spaces?
Martin,
The bug report where the discussion originated is for that very bug (space above and below text causing selection). :)
On Fri, Apr 11, 2014 at 12:34 PM, Martin Owens <doctormo@...400...> wrote:
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:
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.
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
------------------------------------------------------------------------------
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
------------------------------------------------------------------------------ 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