Pointer Input - just not fast enough

[lcamara]

For those of you that do a lot of entering multi-character commands and right-clicking for enter, you'll probably want to turn off Pointer Input (right-click "DYN" on the bottom, then choose "Settings..."). This is why I came to that conclusion:


I just started playing around with 2006, and I noticed that when entering "tr" (for trim) then right-click (enter), only the "t" would get picked up and the text command would start.


At first I thought it was the "time-sensitive" rt-click, so I turned that off (I had trouble with it in 2005, so I've been still using the old-style right-click-is-enter setting).


It still occurred, and since it usually happened while I was moving the mouse across the screen, I thought it was the selection preview, so I turned that off, too. I noticed at that time that the "enter" was generated on the mouse button DOWN event, but I checked & 2005 does that too, so that wasn't it either.


Finally, I realized that the cursor would jump & kind of do weird things when entering commands. It appeared that the right-click down event was taking priority over the keystroke event (maybe the key press is triggered on the up event). Since the Pointer Input window would "freeze" its position once you start typing a command, I figured it might be that - turned it off - and WOOHOO! problem solved.
Now I'll probably go back & give the time-sensitive rt-click & selection preview another shot.

Here's my semi-related wish-list item, "Pointer Input that moves with cursor": http://forums.augi.com/showthread.php?t=19232.

[robert.1.hall72202]

Thanks for posting...........I kept getting an erase command when I was trying to explode an object "EX". What is the purpose of pointer input anyhow? Are we losing anything by
turning it off?

[BrenBren]

For those of you that do a lot of entering multi-character commands and right-clicking for enter, you'll probably want to turn off Pointer Input (right-click "DYN" on the bottom, then choose "Settings..."). This is why I came to that conclusion:


I just started playing around with 2006, and I noticed that when entering "tr" (for trim) then right-click (enter), only the "t" would get picked up and the text command would start.


At first I thought it was the "time-sensitive" rt-click, so I turned that off (I had trouble with it in 2005, so I've been still using the old-style right-click-is-enter setting).


It still occurred, and since it usually happened while I was moving the mouse across the screen, I thought it was the selection preview, so I turned that off, too. I noticed at that time that the "enter" was generated on the mouse button DOWN event, but I checked & 2005 does that too, so that wasn't it either.


Finally, I realized that the cursor would jump & kind of do weird things when entering commands. It appeared that the right-click down event was taking priority over the keystroke event (maybe the key press is triggered on the up event). Since the Pointer Input window would "freeze" its position once you start typing a command, I figured it might be that - turned it off - and WOOHOO! problem solved.
Now I'll probably go back & give the time-sensitive rt-click & selection preview another shot.

Here's my semi-related wish-list item, "Pointer Input that moves with cursor": http://forums.augi.com/showthread.php?t=19232.

I am just not seeing the same issue. I type TR and hit enter and the trim command starts, all while moving the mouse around the screen. Perhaps something else is causing this delay?

[bskripac]

I thought it was just me, I have run into the same issue. I am a typer as well, and when I would be in the middle of a command I will typically type in a snap that is not commonly set when I draw like center or mid. When doing the it would cut me off, so I had to type slowly to get it to work. The good news is that I have almost broke myself of the habit and started using the CTRL + Right-click to get my snaps.

Anyway, I have run into the same issues.

[Spectrefish]

I am just not seeing the same issue. I type TR and hit enter and the trim command starts, all while moving the mouse around the screen. Perhaps something else is causing this delay?
I am not having any delay problems either. What kind of system are you running CAD on?

[jaberwok]

I see a similar delay and it relates to an earlier thread too. I use @ a lot and have been getting unexpected behaviour. I've found that typing "@" pause "0,0,0" (all without quotes) solves the problem.

[Steve Johnson]

Me too. If I quickly type an osnap, e.g. m, i, d, [space], some of the time it doesn't take. I can see the "mid" I entered, but I get no osnap glyph. Then, when I try to reproduce it, it doesn't happen any more...

I'm no speed drafter, so I can see top guns easily getting frustrated by this, hitting that DYN toggle and leaving it turned off.

[lcamara]

Forget about moving the mouse around. Just type a "T", then try your best to hit "R" and then right-click in as rapid succession as possible. (or "E" then "X" & rt-click).

I just noticed something - the second letter is actually displayed in the Pointer Input box! It just doesn't get transferred to the "real" command line.

I'm running on XP Pro SP2, P4w/HT 2.6 GHz, 512 MB (Dell Dimension 4600), and while I plan on beefing up the memory to 1 GB, the other machines in the office are equivalent, or below mine. Although I do plan on buying dual-processor workstations for the cad guys next year, probably w/ 2 GB.

If you still can't reproduce this issue, please post your system info, and any changes you've made to the config (if you remember).

[lcamara]

I can see top guns easily getting frustrated by this, hitting that DYN toggle and leaving it turned off.
Actually, I leave DYN on - I just turned off Pointer Input (in settings). The rest of the stuff seems to work ok for me.

[robert.1.hall72202]

Ive had to change some of my double letter shortcuts......seems very annoying when I type in "EX" and get an "E" for the erase command. Since that is the only command I am having problems with, I am ok since I changed to seomething completely different. When you are speaking in computer lingo, this is should not be something a user should have to do!

[stilesj]

I was finally able to reproduce this with the right-click. The mouse input must just be sneaking in there a split-second before the keyboard input.
However, I'm used to using space bar for my Enter since my hand's already right there for typing and this never misses that second letter. Just another option for those who would like to use the pointer input.

[jaberwok]

This problem is compounded (for me) by the fact that I'm using my laptop for work. I mouse with the left hand and type with the right so my right wrist touches the glide-pad (or whatever) and acad "sees" input from this when I am trying to type. I've disabled the glide-pad drivers but it doesn't stop it.

[lcamara]

...I'm used to using space bar for my Enter since my hand's already right there for typing and this never misses that second letter. Just another option for those who would like to use the pointer input.
There have been several times when I've considered (and tried) using the SPACE BAR instead of ENTER (especially when tables came out). However, I keep going back to using the right-click - partly because I've just used it for so long & I'm used to it - but mostly because the SPACE BAR is just not an ENTER key. I can't come up with anything off the top of my head, but I remember coming across a few situations where the SPACE BAR just didn't work.

I wouldn't be surprised if somewhere down the line the context menu gets some functionality that I just can't live without. But right now I have no reason to change, and "if it ain't broke, don't fix it."

[stilesj]

I would be interested to know if you remember an occasion where the space bar does not serve as Enter for commands. I took a little getting used to it when I first started using it, but have never had a problem with it since.

[jaberwok]

AFAIK, Space acts as Enter unless you are entering literal text as in "this is literal text".
Also, I reckon the spacebar is the only key you can reliably hit with the thumb of either hand.

[Steve Johnson]

Whenever command-line input needs to accept spaces as spaces, it can't use space as Enter. This includes anywhere that AutoCAD is asking for symbol names (e.g. layer names can contain spaces) or wildcards.

[stilesj]

Well, yes, that I understand. But in those cases, would you be using right-click as Enter since you would be more focused on the keyboard, probably with both hands? For any everyday command, I would think space bar should work fine.

[mfowler]

I typically use the space bar for enter as well. I do use right-click on occasion when I'm really in the groove, but I haven't noticed the truncated command phenomenon. What I have noticed is the problem when entering osnap commands. Mid command, I type "end" (example), hit spacebar and sometimes it takes and sometimes not.

[cwade]

I have has no problems with using space, enter or right click as enter and I only have the dynamic display on, I have even turned off the command line to get a little more screen space.