Abort Any Command

[Tom Klaber]

Just like we can cancel a render - we should be able to abort any command.  Occasionally you accidently or on purpose start something that is way too complicated - and it would be good to be able to cancel out of it - essentially a preemptive undo.  

[PVA - Jim]

This will become possible once geometry and mathematics calculations are converted to multicore. For now, it is not possible since the same core that is doing the thing it was asked to do is the same one that monitors input of a STOP command. Luckily however, this is effectively a guaranteed feature though once core support comes.

[Tom Klaber]

Good to know and understand!  Sounds like it is in the works.

[Andy Broomell]

This will be especially helpful for the paint bucket mode of the polygon tool. Sometimes using that in area that's not truly closed results in such a long hang that the only option is to force quit.

[Matt Overton]

7 hours ago, JimW said:

This will become possible once geometry and mathematics calculations are converted to multicore. For now, it is not possible since the same core that is doing the thing it was asked to do is the same one that monitors input of a STOP command. Luckily however, this is effectively a guaranteed feature though once core support comes.

 

Is this "likely" to happen in the near future?

Even in simple forms like asyncing and even delaying complex operations to allow user interaction to continue on main thread.

 

Was surprised Curtain Walls are effectively unusable if you ever need to edit them in 3D. Seeing they seem to try and calculate full geometry of the new wall for every screen frame of user editing. 

[zoomer]

8 hours ago, Matt Overton said:

Was surprised Curtain Walls are effectively unusable if you ever need to edit them in 3D. Seeing they seem to try and calculate full geometry of the new wall for every screen frame of user editing. 

 

Here too,

I tried Curtain Walls for the first time and abandoned them soon.

They even need long time just to be deleted !

[Amorphous - Julian]

In the past, the 'stop process' keystrokes will end all processes immediately.

 

IN VW 2018, following are the processes that we often need to abort, but cannot do so with the 'stop process' [ ⌘ + . ] shortcut keys (or 'ESC')

 

- Hidden line processing in Design Layer View

- Abort 'publishing' of a hidden line render in a sheet

- Abort a 'Renderworks' process

- Too many others.

 

This is an important feature to bring back as the alternative (force quit and wait for VW to restart) hinders productivity. 

Edited September 4, 2018 by Amorphous

[Amorphous - Julian]

I need to bump this post again because we sorely need COMMAND+PERIOD to terminate processes, particularly generating viewport renderings during a publish. 
We've now gone through 3 revisions of Vectorworks since this first post. Can some attention be given to this already? 

[Bill-CollaborativeMT]

I agree. We definitely need a way to abort a command or viewport rendering and with some kind of keystroke. Its 2021 for goodness sake. When using the polygon tool with paint bucket mode sometimes what you think is closed is not and VW tries to fill the world with a polygon. I find that I first save THEN use the paint bucket mode and some other tools every time to avoid the force-quit restore from back-up routine. There are other commands like this. Just basic courtesy to a user to be able to abort a command.