Comment 30 for bug 196453

Revision history for this message
Strangelv (jamesg) wrote :

Okay, so I find this thread and discover that if I press tab a whole bunch of times I eventually find it. Great. Now I still can't rotate it -- just because it needs to be invisible doesn't mean it's not structurally important. And making it non-invisible and then invisible again on every open image I'm needing to go back and fix something with is sufficiently inconvenient that finding my extremely rarely used login to complain here seemed like a good use of time.

I very much would like to be able to click on or alt-click to hit the object instead of wasting large amounts of time trying to work around rules designed for someone else's idea of an optimal workflow. One that evidently never involves the rather basic thing I'm trying to do.

Admittedly, if it wasn't for a different, hopefully less controversial bug I wouldn't be needing to select the invisible object again.

Even if non-visible objects were treated as being at the bottom when alt-click is used that would help enormously, unless I have an outlandish number of overlapping paths to deal with and had it on top or near the top for a reason.

Putting the object in a layer won't work because it needs to be at a specific Z axis and I don't want to need to create five layers to keep things in order and still probably fumble things when it should be able to work with a single layer.

Moving things around is such a big horrible time consuming inconvenient mess to put the object precisely back to its previous location that I don't even know where to begin with explaining why that idea a bad one.

Yes, after reading the condescending attitudes of the pro-bug caucus in here I *AM* a bit grumpy right now.

I'm glad you noticed.

After reading this page I can easily see someone patronizingly explaining why it's important for text put on a path to spontaneously reposition itself away from where I put it, and why I'm being unreasonable for wanting it to stay put when I hit save, and explaining why it absolutely shouldn't show me the change until after I try to reload the image.