Author Topic: Changed Setting...  (Read 5029 times)

0 Members and 1 Guest are viewing this topic.

hudster

  • Gator
  • Posts: 2848
Changed Setting...
« Reply #15 on: December 10, 2004, 10:27:41 AM »
yip, I select the line so the grips are showing, then click button.

the I get a cancel message on the command  line and i have to reselect the line to erase.

It's a real pain, cause i'm used to working the other way and when i'm concentracting i forget to click the button before the objects.

It does this with everything, copy, erase, layiso, etc.
But not if I enter the command from the keyboard, then it works fine.
Revit BDS 2017, 2016, 2015, 2014, AutoCAD 2017, 2016, Navisworks 2017, 2016, BIM360 Glue

M-dub

  • Guest
Changed Setting...
« Reply #16 on: December 10, 2004, 10:53:32 AM »
That's really weird.  I don't know what it could be.
Could you try adding a new custom button and just add _ERASE as the macro instead of ^C^C_Erase.  I don't know if it will make a difference, but it might be worth a try, anyway.

CADaver

  • Guest
Changed Setting...
« Reply #17 on: December 10, 2004, 10:53:57 AM »
Works fine here, unless PICKFIRST=0.

hudster

  • Gator
  • Posts: 2848
Changed Setting...
« Reply #18 on: December 10, 2004, 11:02:41 AM »
tried the new macro button with _erase;

no joy, cancel came up first.  Looks like an unistall is required.
Revit BDS 2017, 2016, 2015, 2014, AutoCAD 2017, 2016, Navisworks 2017, 2016, BIM360 Glue

M-dub

  • Guest
Changed Setting...
« Reply #19 on: December 10, 2004, 11:06:13 AM »
Hey, Hud...
Can you check AND CHANGE the Pickfirst variable?  I'm wondering if it's somehow read-only or....something...

???

rktect3j

  • Guest
Changed Setting...
« Reply #20 on: December 10, 2004, 11:11:03 AM »
Maybe this sounds too simple but have you tried restarting your computer.  Sometimes, I get commands that don't sem to work right so I turn the puter off and on again and all is right in the world.

CADaver

  • Guest
Changed Setting...
« Reply #21 on: December 10, 2004, 11:43:33 AM »
Quote from: Hudster
tried the new macro button with _erase;

no joy, cancel came up first.  Looks like an unistall is required.


First be SURE you don't have some odd-ball reactor running or something, or a redefined copy command.

ronjonp

  • Needs a day job
  • Posts: 7533
Changed Setting...
« Reply #22 on: December 10, 2004, 12:34:13 PM »
Off subject, but....What does the _ before the command do?

Windows 11 x64 - AutoCAD /C3D 2023

Custom Build PC

hudster

  • Gator
  • Posts: 2848
Changed Setting...
« Reply #23 on: December 10, 2004, 02:57:24 PM »
Quote from: rktect3j
have you tried restarting your computer.

That is exactly what our IT support always say.  I think it gives them time to think of something.
Even I say that now when someones asks me a question.

how can I check what reactors are running?

I have a feeling it was a trial hatch creation program I ran yesterday.
Everything worked fine until I tried that program, now this.

I also restored a previous profile, but I still get the same issue.
Revit BDS 2017, 2016, 2015, 2014, AutoCAD 2017, 2016, Navisworks 2017, 2016, BIM360 Glue

MikePerry

  • Guest
Changed Setting...
« Reply #24 on: December 10, 2004, 03:56:10 PM »
Quote from: ronjonp
Off subject, but....What does the _ before the command do?

Hi

Below comes from Stig Madsen (posted today) via the AUGI LISP Forum -

Quote:
Originally Posted by todd.mackay
Sorry to intervene, but what is the difference between "._Circle" and "_Circle" - Also, what does "_Non" do in that same example?


Ever worked with a German localized version of AutoCAD?

Befehl: KREIS
3P/2P/TTR/<Mittelpunkt>: Keiner von ... etc.

"KREIS" is the German CIRCLE command and "Keiner" is the None object snap. Because there are numerous localized versions out there, AutoCAD provides a way to override localized names. This is done by prefixing the native command name with an underscore. By using, say, "_CIRCLE" in an AutoLISP routine (or menumacro or VBA macro) you ensure that it will invoke the CIRCLE command no matter which localized version is being used (same thing with subcommands and object snaps such as "_none").

The dot prefix - or period - is for accessing the original command in case a command has been redefined.

A hyphen will invoke the command line version of an otherwise dialog-based command (if a command line version exists).

So, to invoke the original command line version of a LAYER command - independent of localized versions - you could use the form "._-LAYER"

************

Have a good one, Mike