Re: [Inkscape-user] Inkscape can be extremely frustrating

It can't ever catch all the cases, though. Layers? Groups? Too much blur? A clip or mask? Other objects above in a different layer? There are so many of those that cause drawing invisible objects, and Inkscape doesn't help with determining the cause (btw. opacity at 0 is the most frequent cause, esp. as there is a bug about the opacity indicator field in the current stable version, after that comes 'fill alpha at 0'. 'no stroke, no fill' is a lot rarer, in my experience). I'm sure we can catch some or most of these. I still maintain it's an error to draw a shape with no fill and no stroke, regardless of the reason ... with the possible exception of masking or clipping. I don't see how groups would be a problem unless the group were set to 0% opacity...

another thing whic is inadvisable for all the same reasons. :) Regardless, if the user hits escape twice, it exits out of any groups etc. We should make sure that at least in this condition, where nothing else is interfering, the user is able to draw visible shapes effectively without having to tweak anything to see what they are drawing. :)   - It might be inadvisable, but it's quick and a way that is currently available to change the line width of a line drawing (like a simple cartoon). I wasn't talking about gradients, and also not about shape properties. A better method is to enter the group, select all, and adjust the line-width there. Being able to set the stroke, but not stroke gradient, or fill but not fill gradient on a group is inconsistent behaviour and needs to be fixed one way or the other - either the group is treated like selecting all its contents, or the group needs to be treated like a separate shape. Right now its both, and is confusing and inconsistent UX.

  I just don't expect Inkscape to add a stroke when I change the line width - I understand that it might help new users, but it's also illogical. Currently, if the user adjusts the line width and there's no stroke, the value is thrown away entirely. That's absolutely apalling UX. :)