Problem with previous commands in the Command Line
Problem with previous commands in the Command Line
(OP)
Hello Community,
I'm a long time AutoCAD user, and recent Draftsight convert. I've run into an issue that I believe to be a bug, but could be an option in Draftsight that I don't understand yet.
The issue is that when I enter a command in the command line, DraftSight will occasionally start the previous command but add the command I am trying to use as a prefix. I know it sounds a little strange. For example, if I try and initiate the "copy" command, but the previous command was "move", sometimes Draftsight will initiate the move command, but the command line will read "cMOVE" and the move command will be active. This doesn't happen all the time, only occasionally.
Is this a bug or a feature that I just don't know yet?
Thanks community.
-Jeff
I'm a long time AutoCAD user, and recent Draftsight convert. I've run into an issue that I believe to be a bug, but could be an option in Draftsight that I don't understand yet.
The issue is that when I enter a command in the command line, DraftSight will occasionally start the previous command but add the command I am trying to use as a prefix. I know it sounds a little strange. For example, if I try and initiate the "copy" command, but the previous command was "move", sometimes Draftsight will initiate the move command, but the command line will read "cMOVE" and the move command will be active. This doesn't happen all the time, only occasionally.
Is this a bug or a feature that I just don't know yet?
Thanks community.
-Jeff





RE: Problem with previous commands in the Command Line
You've got to hit <ENTER> (or Spacebar) an extra time in DraftSight to close some commands. I haven't delved into it deep enough to know if you can turn off that requirement.