Wacom Tablet, very often a select behaves as if the button is continuously pressed so even if you lift up the pen it still keeps marquee selecting as if it was pressed.
The only way to get out is to click again to mark the marquee range, or cancel.
It happens only if objects are clicked on, empty space will not trigger this bug.
I never got this behavior with a mouse.
Tracked the bug!
As I was writing this and testing it I just managed to track down when this is happening. Click+drag is the culprit. I can replicate this 100% now, both mouse and tablet. Basically if it’s not a steady click, but a click and drag this bug kicks in. On tablets it’s much easier to get an accidental drag after a click, that’s why this bug is (seemingly) present only on tablets. Edit:
Just tested with the default cube and it does not happen. The other key to reproducing this bug is the polycount.
7 subdivisions on the cube will trigger this bug!
Anyone know for a workaround/setting for this bug?
Windows7 64
blender version: 2.5+ (present in all versions from what I know)
Did you turn off win7’s tablet ‘features’? They get in the way, so turn those off.
I feel it’s not really a bug; it’s because of the opengl lag. The viewport (GUI) cannot keep up in real-time, and this results in Blender capturing the click event, but since our hand will move a bit, the lag causes a click & drag event.
Herbert123, thanks on the reply and the suggestions.
it’s not a win7-tablet ‘feature’ (nicely said BTW), i disable that first thing after a reinstall. it’s also present on winXP.
i think your second guess might be on track. if this is true, all we need is to expose that setting in the user preferences so one can tweak it to the optimal value!
it’s quite a big bug, it gets into way of using blender with a tablet as it’s very hard to do a steady click on a tablet, it becomes that sensitive on higher poly scenes.
i also use blender with the maya input, here LMB is the default for a marquee select. i don’t know what is the key on default blender input.
Just a note that I’ve reported this to the bugtracker and Sergey Sharybin jumped on it and solved it by exposing a setting that fixes this. If anybody else had an issue with this here’s the fix.
From Sergey ‘Patch was just commited to svn rev42483, so it’ll be included to upcoming RC build and official 2.61 release.’
Blender User Preferences > Input > Tweak Treshold (at the bottom left)
Increase value. In my case I’ve maxed it out at 200 and this works well.