On Wed, Feb 07, 2007 at 08:27:42AM -0600, Aaron Spike wrote:
Johan Engelen wrote:
Still, if someone thinks up a good solution to the, in my opinion profound, usability issue of hidden objects; I would be happy to implement this.
I've thought of a couple things that might help. The first few probably aren't great solutions. All of these things apply equally to locked objects too.
- Remove the hide button from the object properties :-)
- implement a "unhide all" verb
An "unlock all" verb might be worth doing too, if there isn't one already. Yesterday we had someone accidentally lock something, not realizing what it did. I walked him through fixing it via the XML editor, but an ordinary user probably wouldn't know to do this. I wasn't sure if there was already a functionality to remove locks, but I didn't spot something obvious in poking around.
- submenu for hidden objects which lists them and allows selection
(could be a little dialog too)
- I think the coolest thing to do would be to implement a little object
browser dialog that allows filtering by xpath or some other type of useful expression. Users wouldn't have to see the xpath for it to be useful we could have a few saved searches, like "hidden objects". But it would be nice if power users could program their own filters, maybe like "redish objects" etc.
Yeah, this sounds very handy. Could be a bit of work to implement, but would really make inkscape handy for managing really large docs.
Bryce