[v2024.1 SP2] Constant software crashes working offline

ok, finally found a solution......Put in a BREAK point and run to that point with CNTRL "U"

What I was doing before was highlighting a certain block of CODE and hitting CNTRL "E" to just run what I had highlighted.....PCDMIS didn't like this at all and kept crashing.

If you just put a break point where you want it to stop, then hit CNTRL "U", no issues...

ok, finally found a solution......Put in a BREAK point and run to that point with CNTRL "U"

What I was doing before was highlighting a certain block of CODE and hitting CNTRL "E" to just run what I had highlighted.....PCDMIS didn't like this at all and kept crashing.

If you just put a break point where you want it to stop, then hit CNTRL "U", no issues...

If you are highlighting a block of code, you should be using CTRL+L (Execute Block).  CTRL+E is only meant for executing a single feature at a time, which is why you had problems.  It shouldn't have crashed but it was never designed to work in the way you were trying to use it.

Neil Challinor Is it possible to add some sort of failsafe check to CTRL+E? 

"If selectedcommands > 1 just execute the first command in the selection" - as opposed to crashing.

There are many internal paths an execute feature can take. I ran a simple test with multiple MOVE/CLEARPLANEs before/after features. I highlighted commands and performed the CNTRL-E using v2024.1SP2. Naturally I did not crash.
Sending the files which are causing issues to tech support with detailed steps helps determining and correcting these crashes - especially if they happen offline.

It could be the combination of the commands being used. 

Or command mode vs summary mode. 

Files would include PRG, CAD, PRB, maybe registry settings.

Just my .02 worth.

If CTRL+E was never designed to execute a block of code, it should not be available when a block of code is selected. If it is, this behavior should be considered as a bug.

It's definitely "CNTRL-E" that's causing my issues.....hasn't crashed since I stopped using CNTRL-E.

Now, I just put a BLOCK at where I want it to stop and I use CNTRL-U.....problem solved.....

It's definitely "CNTRL-E" that's causing my issues.....hasn't crashed since I stopped using CNTRL-E.

Now, I just put a BLOCK at where I want it to stop and I use CNTRL-U.....problem solved.....