Troubleshooting
Why the Vision Text Area Touch Keyboard Stops After 7.8.0
Short answer
On Ignition 7.8.0 the Vision Text Area fails its touchscreen permission check, so the on-screen keyboard never opens for it while every other touch component keeps working. The fix shipped in 7.7.7 and reached the 7.8 line by 7.8.2. Until the Gateway is upgraded, a one-line mousePressed script calling system.gui.showTouchscreenKeyboard restores input.
On this page
- What the failure looks like on the panel
- Check 1: is the client actually in touch mode?
- Check 2: walk every other touch component
- Check 3: confirm which Gateway version is serving the client
- Why only the Text Area ignores touch
- The interim fix: one line of script
- The real fix: upgrade the Gateway
- Questions asked
After a Gateway upgrade from 7.7.3 to 7.8.0, Vision Text Area components stop opening the on-screen keyboard when an operator touches them, while Text Fields, dropdowns, buttons, tab strips and Power Table click scripts on the same client keep working. The cause is a defect in the Text Area's touchscreen permission check: on 7.8.0 it evaluates as not permitted even though the client is in touch mode. The vendor fixed the component in 7.7.7, and the fix reached the 7.8 line by 7.8.2 at the latest. Until the Gateway is upgraded, one line of script on the component's mousePressed event restores the keyboard. Three checks separate this defect from the configuration faults that look identical on the floor, and the last one stops a wrong-Gateway test from telling you the bug does not exist.
What the failure looks like on the panel #
The operator taps the multi-line entry box and nothing happens: no keyboard and no usable caret, because there is no physical keyboard either. Three faults produce that exact screen, so identify the failing component type before touching any setting.
| Screen behavior | Components affected | Likely cause | Go to |
|---|---|---|---|
| No keyboard on any text input | Text Field and Text Area | Client not in touch mode | Check 1 |
| Text Field pops its keyboard, Text Area does not | Text Area only | 7.8.0 Text Area permission defect | Checks 2 and 3 |
| Works from the desk, fails on the panel | Text Area | Test client on a different Gateway version | Check 3 |
| Keyboard opens twice on one press | Text Area carrying the script | Workaround left in place after the upgrade | The real fix |
Two failure classes exist. A client-mode fault hits every touch-enabled input on the window. A component fault hits one component type while client mode is correct, and that is what this is: in the affected project, tab strips, buttons, dropdowns, Text Fields and Power Table click scripts — five of the six input types in use — kept responding, and only the Text Area went silent. On a touch-only station built to run a Vision client as the machine HMI, that one dead box is the whole input problem, because nothing else on the panel can take the entry.
Check 1: is the client actually in touch mode? #
The on-screen keyboard only opens automatically when the Vision client is in touch mode. Two project properties control that, both under Project > Properties > Client > General in the Designer:
| Setting | What it does |
|---|---|
| Touch Screen Enabled | Lets the client run in touch mode and puts the touch-mode option on the login screen |
| Active on Startup | Starts the client already in touch mode, with no login-screen selection |
| Touch-mode choice at login | Per-session selection made by the operator; without it, no keyboard pops |
Read the combination like this:
- Both boxes unchecked: no input on the window will raise a keyboard. Enable both, save, relaunch the client.
- Only Touch Screen Enabled checked: touch mode depends on the operator picking it at login, and a client that auto-logs in never shows the login screen, so it never gets the choice. Check Active on Startup on dedicated panels.
- Both checked and Text Fields still pop up: client mode is correct, move to Check 2.
The same dialog carries a version tell. In 7.8, a Scrollbar Width (pixels) field sits between the two checkboxes; if your dialog does not show it, the Designer is connected to a pre-7.8 Gateway, which is exactly the trap Check 3 closes.
Check 2: walk every other touch component #
Open a window that contains each input type and tap through it on the panel, not with a mouse:
- Text Field: does the keyboard pop up?
- Dropdown, button, tab strip: do they respond to touch?
- Power Table: do the click-event scripts fire?
- Text Area: does the keyboard pop up?
If everything responds except the Text Area, then client mode, the touch driver and event dispatch are all healthy, and the fault is inside the component's own decision to show the keyboard. If the Text Fields fail as well, you have a client-mode fault: go back to Check 1 and relaunch, because saving project properties does not change a client that is already running.
Check 3: confirm which Gateway version is serving the client #
This check kills the false negative. A Designer or test client on your desk can be connected to a different Gateway than the production panel.
Worked example with the real values from this failure: the office install was upgraded to 7.8, but the client launched from it still pointed at the plant Gateway on 7.7. The Text Area works on 7.7 — the defect is not in that build — so the desk test 'proved' there was no bug while the panel, served by the 7.8.0 Gateway, kept failing. One press only means something when the client under test connects to the same Gateway version as the failing panel.
Read the version each Gateway reports on its web page, from the desk and from the panel, and compare:
| Gateway version | Text Area keyboard | Action |
|---|---|---|
| 7.7.3 | Works | The baseline this upgrade came from |
| 7.7.7 | Works | Carries the fix on the 7.7 line |
| 7.8.0 | Broken | Upgrade, or script each Text Area |
| 7.8.1 | Stated port of the fix | Verify one Text Area here before deleting any script |
| 7.8.2 | Fixed | The certain minimum target on the 7.8 line |
Why only the Text Area ignores touch #
A Vision input component decides on each press whether to open the on-screen keyboard, asking whether the client is in touch mode and whether touch input applies to this component. The Text Field and the Text Area run that check separately, and on 7.8.0 the Text Area's evaluation of the touchscreen permission returned not permitted while the client was in touch mode.
The press still arrives — focus moves and mouse events fire — only the automatic keyboard launch is skipped. That explains the two facts that make this bug confusing: the project properties and every other component look correct, and a script on the Text Area's mousePressed event still runs, so the keyboard can be opened from script with the broken check out of the way.
The same component failed the same way on an earlier Ignition upgrade, so add one Text Area tap to the acceptance test after every upgrade of a touch-only project.
The interim fix: one line of script #
On 7.8.0, put this on the Text Area's mousePressed event handler:
event.source.text = system.gui.showTouchscreenKeyboard(event.source.text)
The line hands the component's current text to the built-in on-screen keyboard and writes back whatever the operator enters. It works because the defect only gates the component's automatic launch; the script calls the keyboard directly.
Two limits to respect:
- The handler is per component. Every Text Area on 7.8.0 needs its own copy, and so does every one you place while the Gateway stays on that build. Copy an already-scripted Text Area rather than dropping in a fresh one, so the handler travels with it.
- Every copy must come off after the upgrade. On a fixed build the component opens the keyboard itself, and the leftover handler opens it a second time on the same press.
If you would rather own the whole input surface, you can build an on-screen keyboard from bitmap HMI assets in a popup window and stop depending on the built-in one.
The real fix: upgrade the Gateway #
Back up the Gateway, take the upgrade inside a planned window, and re-test every touch input before the station goes back to the operator — a touch-only panel with a dead Text Area has no other way to enter data.
The decision by situation:
- On 7.8.0 with an upgrade window: move to 7.8.2 or later and skip the scripts entirely. If you stop at 7.8.1, tap one script-free Text Area first — the stated port makes it likely fixed, but the press is the proof.
- On 7.8.0 with no window soon: script the Text Areas that matter now, keep adding the handler to new ones, and book the upgrade.
- Forced off 7.8.0 immediately: 7.7.7 is the 7.7-line build that keeps the fix. Falling back to 7.7.3 restores the keyboard too, but it puts you back on the version you just left.
Either path ends the same way: the keyboard opens on touch, and no handler is left on the component.
Questions asked
Why did the Text Area work when I tested it from my desk machine?
Your test client was almost certainly pointed at a different Gateway than the panel. Upgrading the Designer or a local install on your desk does not upgrade the plant Gateway, and a Vision client runs against the Gateway it connects to, using that Gateway's build. Reproduce the fault from a client on the same Gateway version as the failing panel before you conclude anything.
Does this bug affect Perspective or the built-in numeric keypad?
No. The defect is in the Vision module's Text Area permission check on the 7.8 line; other input components and the built-in keypad are untouched. An on-screen keyboard that fails to appear in a Perspective session is a separate problem with its own client settings on the 8.x platform, not this bug.
Is there a project setting that repairs the Text Area keyboard on 7.8.0?
No project property repairs it. Touch Screen Enabled, Active on Startup and the login-screen touch choice only decide whether the client runs in touch mode; the Text Area's permission evaluation is part of the 7.8.0 build itself. The two ways out are the Gateway upgrade or the per-component mousePressed handler, and every other setting change is wasted time.
Should I put the workaround script on Text Fields too, for consistency?
No. Text Fields pass their own permission check on 7.8.0 and open the keyboard without help. Adding the handler to a component whose automatic launch already works can raise the keyboard twice on a single press. Apply the workaround only to Text Areas on the broken build, and remove every copy after the upgrade.