...

Perhaps this is a misunderstanding: It should deselect any selected

nodes

...

(they must become all gray), but not deselect the shape itself (why

would

...

you need that in node edit?) If you need to edit nodes of another shape, however, you can click on it, and it will be selected instead (i.e. the

old

...

shape's nodes will disappear, and the new shape will show its nodes, initially deselected (gray)).

The reason you need to be able to click on the canvas to not see the nodes is if the shape you are editing has many nodes and it becomes hard to see the original shape or curve or whatever. Trust me, it is really helpful to be able to deselect quickly by clicking on nothing (aka, the canvas).

In node edit, you're supposed to work on nodes, so naturally it displays nodes for you. Just press f1 or f3 or space if you want to "hide" nodes. Or open a new view where you can switch (ctrl-tab) for a quick look without any noise - this way you won't even lose your selected nodes when you switch back. These and more are all natural ways to do what you want, while deselecting _object_ in _node_ edit does not seem quite legal to me.

On the other hand, I might program it so that on the first click it deselects any nodes, and on the second click, deselects the shape (hiding its nodes). However I'm reluctant to do this because this may lead to occasional unintended deselections that may be quite annoying. Anyone else has an opinion?

_________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2f...