m.prestel

Just a warning. Changing the generated csp and attributes on the iframe may allow bad people to run a DOS on your PLC causing a crash or loss of data. All these settings have been chosen to protect the user.

Just a warning. Changing the generated csp and attributes on the iframe may allow bad people to run a DOS on your PLC causing a crash or loss of data.

You should not run the testscript in the normal mode, but in debug (should be the button next to the normal run) BR Marcel

Hey, If you are in contact with Scott, I see no reason why questions should be answered twice. Best regards, Marcel

Not gonna claim this is the "right" way. But we have some challenges ahead and the right way may change ;) You can find an example for the IKeyEventHandler. If HandleKeyEvent returns true, the key press will be dropped. Important: Make sure to call the PRG by adding it to the "Call after visu initialization" in the visu manager. Best regards, Marcel

Not gonna claim this is the "right" way. But we have some challenges ahead and the right way may change ;) You can find an example for the IKeyEventHandler. If HandleKeyEvent returns true, the key press will be dropped. Best regards, Marcel

Oh I see, that will make things way more difficult ;D Assuming that they display keys are mapped to a tab+enter/return (which it looks like since the action is executed), we could filter out the enter/return key. You think that would solve the problem and you could use the normal keyboard handling? Best regards, Marcel

If you are using a target visualization (a panel with a screen and the runtime is running on that panel) then the CODESYS IDE has no part in handling events. This is all done by the visualization, which collects the events, passes them to IEC where the visu task handles them and then draws the changes to the screen again. Anything special which did not work? Yes, the selection example is controlling the keyboard handling, which you do have to activate.