Community
Participate
Working Groups
Build ID: M20070921-1145 Steps To Reproduce: 1.Open some code 2.hands off the keyboard 3.mousedown on some code element, say a classname 4.drag across the name (but don't release the mouse) 5.press Ctrl 6.release the mouse More information: So, this happens to me a lot. I want to, maybe, copy some text. So I start my drag across it, then, in anticipation of typing Ctrl-C, press the Ctrl key - only I did so before letting go of the mouse button, so as soon as I let up, I'm somewhere else in the code entirely. I think the rule should be as stated in the Summary; with the current rule, to avoid this problem I need to insert a little latency into every action. The sequence of my actions is unnecessarily constrained by the current rule. Maybe I can graph this... Mouse Hand: | DDDDDDDDDDDDD Keyboard Hand: | ^^^^^C versus Mouse Hand: | DDDDDDDDDDDDD Keyboard Hand: | ^^^^^C I want both of these sequences to produce the same result: select and copy. I'm flagging it as Windows, because that's all I've got in front of me at the moment, but I think I've noticed this on Mac, too.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
