scripts in civ3d 2023 not starting another command while in a command with ^C^C

scripts in civ3d 2023 not starting another command while in a command with ^C^C

Satoews
Advocate Advocate
382 Views
3 Replies
Message 1 of 4

scripts in civ3d 2023 not starting another command while in a command with ^C^C

Satoews
Advocate
Advocate

Hello everyone!

 

So i am trying to get on my feet in civ3d 2023 and one thing i have notice that in 2018 this script: ^C^C_CC1 which is just a quick lisp to creat a block and place it would end the command and start it again if I pressed the button another time. In 2023 it will stay in the command no matter how many times I press it and I need to manually press the escape button to get out of the command. I am guessing there is a added variable that make this happen anyone know what they added?

Shawn T
0 Likes
383 Views
3 Replies
Replies (3)
Message 2 of 4

ВeekeeCZ
Consultant
Consultant

So why you don't simply remove them? They are not necessary to run a lisp/macro.

0 Likes
Message 3 of 4

Satoews
Advocate
Advocate

I would like it to end the previous command when hitting the script. is there a way of doing that other than having ^C^C before the command?

Shawn T
0 Likes
Message 4 of 4

Kent1Cooper
Consultant
Consultant

You describe it in terms of your hitting that button when you're already in what that same button invokes.  I agree it should cancel that command and start it again, but questions arise:

 

Does it work to cancel other commands and start that one, if you pick the button when you're in, say, a LINE or MOVE command?  Or is it only itself that it doesn't cancel?

 

Dumb question:  Does the command it calls up use a dialog box that's waiting for input?  I don't think you can call a macro with a tool palette button when a dialog box is up that needs attention.  [A dumb question because it sounds like the way it used to work would not involve such a thing.]

 

And maybe this is also a dumb or even insulting question, but just to be sure:  Are you seeing enough lines of command history to know that it's really not cancelling and starting again?  With few enough lines showing, and depending on what its displayed bits are [prompt, etc.], it could be cancelling and starting over and putting up the same prompt [or whatever] again, and look the same in the command line as if it had stayed in the previous calling of it.

Kent Cooper, AIA
0 Likes