[Bf-funboard] Bf-funboard Digest, Vol 79, Issue 9

[jin.choung]

On Jun 9, 2012, at 3:00 AM, bf-funboard-request at blender.org wrote:

> In a complex scene you have an object selected. Then you decide to work 
> an another part of the scene, the selection is not visible in your 
> viewport. Accidentally press X.

is this actually something that happens?

I've worked with maya and lightwave for over 15 years and it's never once been an issue. 

especially since a new selection will deselect the previous one unless you're specifically invoking multi select, is it very likely you would be working in another part of a complex scene without making selections?

the two differences with blender which could conceivably contribute to this problem (and therefore, the proposed solutions) is:

1. something is always selected in blender. you have no DESELECT ALL state which is natural in most apps (although lightwave layout also shares this quality).  why not allow "nothing" to be selected in blender?

2. x key as delete. conceivably this key is designated delete for the sake of speed but if people are running into issues where they're "accidentally" deleting things, the less intrusive solution would be to use the actual delete key on the keyboard rather than a confirmation. you have to consciously SEEK the delete key so little chance of inadvertent hit.  also, very rarely do you need to be deleting things like crazy to necessitate such an easily accessible  xkey delete and in circumstances where you are constantly deleting, you just keep your finger on the delete key.