[DEBUG] Cursor in Scripting

I have installed the build b2019021202 on Windows Server 2016.
When I opened a designer on a Windows 10, I noticed a strange behavior on editing a script: the cursor does not match the screen position.
I tried to open a designer on Linux and the behavior is ok.
I post a video to better clarify.

ScriptEditor.zip (407.8 KB)

Thank you so much.

@andrea.morando this should be fixed in the todays build. Upgrade the build and clear out the runtime cache for your client/designer in .ignition/cache/resources/ (delete the runtimes dir there) and relaunch. It will grab an updated version of the runtime from the gateway. Let me know if there are any other issues. once you confirm it go ahead and mark this as solved.

Jonathan C


Thank you Jonathan. Now it works fine!


I’m having a very similar problem: Anywhere I click, the cursor ends up off to the right of wherever I clicked, further right the further into the window it is. I’d say the effect is maybe only 2-3% off.

A second oddity: On lines with long strings in them (no non-ASCII characters), the cursor will go completely off the rails, again floating to the left of where it actually is, as in the video posted above. It only seems to happen around long strings; long lines of code will keep the cursor where it’s supposed to be, even if it doesn’t match where I click. The effect is very small, maybe only 1%, but it eventually passes multiple characters.

At first I was thinking it was because I’m logging into Server 2012R2 to develop, but I just tested entirely locally and get the same behavior.

Windows 10 1809, monitor is 4K at 175% zoom. Latest nightly build.

This problem has happened in the past. Sometimes the problem persists after it has been fixed in the patch.

The resolution for that problem is to clear your cache. See this thread.

1 Like

I actually removed the entire .ignition folder and started from scratch on my local workstation first. No cache, everything was rebuilt from scratch. Good to see there’s a specific bug thread for it though, I’ll follow up there.