kewakl (Customer) asked a question.
PAC Suite 3.0.8.14 Multiple errors caused by CTRL-Z
While editing rungs 166-168, I pasted a contact incorrectly. I hit CTRL-Z - possibly twice.
The errant paste remained. I looked around and found a couple errors.
Rung 161 was missing the first output branch -- it was replaced with a horizontal, a rising vertical followed by another horizontal connector, which was reallllllly long. The horizontals were difficult to remove with SHIFT+CONTROL+arrow. Could there have been multiple overlaid?
Rung 232 was missing a math instruction.
Why CTRL-Z went to those rungs, I do not know. I have not messed with them today.... Well, until CTRL-Z deleted somethings.
Also why does rung 233 indicate error for backward flow?
Can you PM me an online system report so I duplicate and get over to our development team for review?
I typed up that exact same rung and compiled without issue.
>Can you PM me an online system report
Good call, I did not think to check if I could reproduce the issue. I can.
Just delete the MATH instruction in Task 'Process' at Rung 232
I will be sending the project shortly.
deleting the incomplete rung does get rid of both errors and compiles.
I am asking development why the "backward flow" error occurs.
>deleting the incomplete rung does get rid of both errors and compiles.
Yes, deleting the incomplete rung descender does clear the error but the rung only BECAME incomplete because of an improperly executed CTRL-Z UNDO.
Adding back the improperly removed MATH instruction fixes this part of the original issue.
The software undid something that it SHOULD NOT have undone.
I was not and had not been working with that rung, so there should be no reason for this activity to have been in an undo stack.
Could there have been some disconnect between the contents of the undo stack and the actual target rungs pointed to by the undo stack - after adding/inserting rungs?
That rung (with the MATH instruction) has been in place since mid-April. I know this because I opened an old rev of this project to see what was there previously.
>I am asking development why the "backward flow" error occurs.
Please do not overlook the software's mishandling of the CTRL-Z UNDO that caused this error to be generated.
Thank you.
I've noted some odd behavior like this. And as I recall, an errant mouse click invoked "something" that destroyed a rung (it disappeared). I chalked it up to maybe being careless. I just closed the program without save, and started over.