Entity selection bug

When selecting entities by window\crossing\etc. and you touch the same entity again, it is removed from the selection set. It is realy very annoying. Previously the removing from the selection set was done by combination with the SHIFT key.

Comments

  • It has always worked like that for me, the only difference is lately if you have a touchy input device (like the wacom stylus) you can accidently double pick and it can move slightly.I find it useful sometimes to pick one or more entities before window picking everything in an area, which then de-selects the first set... the ones I did not want selected. More often I want the majority of entities in an area selected so it's quicker to pick out those not wanted first.

  • What you mean is, to think from end to start, rather to think straigt down the path. Like you I like to select the bigger part of the entities, and then to remove the smaller that I don't need. The difference is, that first I select the entitities and then with the help of the SHIFT key, I can fine tune the selection set.

  • The straight picking/deselecting operation has always behaved the same I believe. I never used the shift or ctrl keys method but I could never see what advantage when you could just keep picking.Just noticed that ctrl/drag copies all gripped entities while just dragging moves them, which isn't much help without snaps and as previous it makes selecting too touchy.

  • Up to version 5.0 it behaved just as in AUTOCAD. There is logic in the way you pic the entities. First to pick as mutch as you can, by window\crossing and so on, and only then to remove the unwanted ones by picking them one by one.

  • For the record: nothing was changed to the selection behaviour between v4 and v5. I just checked back with some v4.x builds and the selection behaviour was just like it is today in V5.Still, this is an interesting discussion because the selection behaviour indeed looks more straightforward and predictable if a single click on an entity always would select the entitiy and a shift click always would deselect the entity. Any objections?

  • I'm confused, I still have Icad98 installed and shift contributes nothing when selecting/deselecting. My V5 behaves the same - pick to select, pick again to deselect.Oh just realised in V5 shift click prevents the selection state from being changed - can't see the point of that. I agree it would work better as you propose.The recent feature (V4/V5) of double clicking to bring up entprops is handy but the darn things often move slightly and that's a real nuisance. Also Entprops butts in too often when not required, such as when moving a grip.

  • Selecting entities with by way of window/crossing will triger the grips of all objects selected. To remove any one in particular, you have to hold the SHIFT key and pick the object with the left key of the mouse. Reselecting the same object again, is done the same way.

  • Again, the shift has no effect in my 5.0.0023. I can select then deselect just by picking again, or could until I got a Wacom tablet. Now I can only deselect using a window or crossing (I believe it has to do with the speed and operation of the stylus), but shift still has no effect. Shift/pick also had no influence with the Logitech trackball I used until recently. Maybe it has to do with input devices although the trackball mirrors a mouse in every other regard.

  • This feature is not documented in any book. Only by roaming forums of LISP programing you can find tips like this. This feature works in AUTOCAD just fine with most of thetablets that I know of. In BRICSCAD it works fine, only if you preceed the command before picking the entitities. Maybe the answer is in changeing some variables, so it will behave just as in AUTOCAD.

  • Ah, the hint was "with the command issued first". I had seen many references to it and used it on rare occasions, I usually use grips, and got so used to not having the shift pick (from acad 2.5 - not sure when the trick was introduced) that I usually forget it when using command-first.

  • I noticed the "movement" thing a few years ago and began picking the "process" first instead of the entity in order to avoid the movement.

  • Because no one else had mentioned it, I had sort of assumed I was the only one to find it a problem. Without much programming knowledge sometimes I wonder if certain minor annoyances are not the result of compromises for the greater operating good.

This discussion has been closed.