How Do You Configure TRI-PLC Mouse Wheel Scrolling?

One mouse-wheel detent produces an input event, but the TRI-PLC source-code viewport moves only when that event reaches the Java process hosting the editor and is translated into a scroll action. The number that matters is whether each wheel input causes visible vertical movement while the source pane has focus. PLC scan time, I/O state, and communications are outside this path; this is desktop event routing, not controller logic.

Wheel-Event Path

The operating system first receives the mouse-wheel event and directs it to the active application window. The application must then associate that event with the source editor's vertical viewport. In the reported configuration, TRI-PLC did not provide the expected source-code movement directly, so an application-specific mouse-wheel utility supplied the missing association.

The utility must target Javaw.exe in the Java directory. That target matters because a Java graphical application can be launched through Javaw.exe; assigning the wheel action only to a shortcut, project file, or unrelated launcher leaves the actual editor process unchanged.

Quantity or state	Required result or limit	Where to read it
Wheel-event response	Nonzero vertical source movement per wheel action	TRI-PLC source-code pane
Keyboard fallback	PgUp and PgDn move through the custom-function editor	Visible editor viewport
Mapped executable	The Javaw.exe instance that launches the editor	Java installation path and running-process details
Focus state	The source-code pane, rather than a dialog or another window, receives input	Active-window highlight and caret position
Trial period described for the tested utility	30 days	Utility licensing screen
Purchase price described for the tested utility	$14.95	Utility licensing screen; verify current terms before purchase

Supported Navigation Approaches

Two approaches solve the navigation problem at different layers. The mouse-wheel utility changes desktop input handling for the application. The keyboard method uses editor navigation already available while editing a custom function.

Approach	Configuration	Dependency	Best fit	Main limitation
Application-specific mouse-wheel mapping	Assign wheel control to Javaw.exe	Third-party desktop utility	Frequent source navigation where wheel operation is preferred	Mapping the wrong Java executable produces no change; executable-wide rules may also affect other Java applications using that copy
PgUp/PgDn	No added software	Keyboard and editor focus	Immediate navigation in a custom-function editor	Page-sized movement is less granular than a wheel

Use PgUp and PgDn first as the baseline test. If those keys move the source correctly, the editor viewport and document remain responsive. Add application-specific wheel mapping when continuous mouse navigation justifies another desktop component.

Recommended Decision Path

The preferred configuration is the application-specific mapping when the engineering workstation regularly edits long TRI-PLC source sections and the wheel is the normal navigation device. Its condition is precise: the assignment must point to the Javaw.exe that actually hosts the running editor.

Keep the keyboard method available even after the mapping works. It separates an input-assignment failure from an editor failure: if the wheel stops but PgUp and PgDn still work, troubleshoot the mouse, focus, utility, and executable selection. If neither input method moves the source, investigate the active pane, modal dialogs, document state, or the editor itself.

On a shared engineering workstation, also consider mapping scope. A rule attached to an executable can apply to every application launched through that same executable. Test another Java application after enabling the rule; unexpected scrolling there indicates that the rule is broader than the TRI-PLC window.

Process and Focus Prerequisites

Close unrelated dialogs and click inside the source-code pane before testing. The caret or selection should appear in that pane. A wheel event sent while a project tree, menu, message box, or another application owns focus may be handled elsewhere even when the mapping is correct.

Identify the Java executable used by the active TRI-PLC session. Multiple Java installations can place several files named Javaw.exe on one workstation. Selecting a same-named file from a different Java directory creates a valid-looking rule that never receives the editor's events. Read the executable path from the running process when the operating system exposes it, or compare the Java path used by the editor's launcher with the path entered in the utility.

Record the chosen path before changing the mapping. This gives the workstation owner a repeatable configuration and makes later Java upgrades easier to diagnose. An upgrade or reinstall can move the launcher to another Java directory while leaving the old mapping intact.

Application-Specific Mapping Procedure

1. Launch TRI-PLC normally and open a source section long enough to require vertical scrolling.
2. Click inside the source-code pane and verify that PgUp and PgDn move the viewport. This confirms that the document can scroll before adding the wheel layer.
3. Determine the full path of the Javaw.exe process associated with the running editor. If several copies exist, match the active process rather than choosing by filename alone.
4. Open the mouse-wheel utility and create an application assignment for that exact Javaw.exe.
5. Configure the assignment to translate vertical wheel movement into the utility's vertical scrolling action. Control names vary by utility, so select the action that moves the active window up and down rather than horizontal scrolling or pointer movement.
6. Apply the assignment. Restart the editor or the utility only if the configuration does not attach to an already-running process.
7. Return focus to the source-code pane and test upward and downward wheel movement.
8. Open another source section or custom function and repeat the test. A rule that works only in one pane may be interacting with focus rather than providing an application-wide assignment.

The utility described with the working setup offered a 30-day trial and a stated purchase price of $14.95. Treat those as the terms of that tested package at the time described, and read the current licensing screen before deployment.

Keyboard Navigation Procedure

The built-in alternative requires no input remapping. While editing a custom function, place focus in the editor and press PgDn to move toward later source lines or PgUp to move toward earlier lines.

1. Open the required custom function.
2. Click in its text-editing area so the pane owns keyboard focus.
3. Press PgDn once and observe the page-sized downward movement.
4. Press PgUp once and verify that the viewport returns toward the original position.
5. Use the caret keys or mouse selection after reaching the required source region.

This method is also the fastest diagnostic reference. When page navigation succeeds but the wheel fails, source loading and vertical viewport movement are functioning. The unresolved layer is the wheel-event path.

Functional Verification

Verification must distinguish movement, direction, focus, and persistence. A single successful scroll with one document open proves only that an event reached that pane once.

Test	Expected observation	Failure points to
Wheel down in source pane	Later lines become visible	Missing rule, wrong executable, inactive utility, or focus problem
Wheel up in source pane	Earlier lines become visible	Incorrect action direction or incomplete assignment
PgUp/PgDn test	Viewport moves by pages	If both fail, the issue is above the mouse-mapping layer
Second custom function	Same wheel behavior	Pane-specific focus or component handling
Editor restart	Mapping remains active	Rule was not saved or utility did not start
Workstation restart	Utility and mapping return as configured	Startup or configuration persistence problem
Other Java application	No unwanted navigation change	Executable-level rule has broader scope than intended

Finish by navigating in both directions several times without clicking another window. Watch for reversed direction, excessive movement, missed events, or scrolling in the wrong pane. These observations identify action configuration problems that a simple pass/fail test misses.

Failure Modes and Corrections

No movement after assigning Javaw.exe: Compare the mapped path with the executable path of the active editor process. Same filename does not mean same Java installation. Then confirm that the utility is running and that its assignment is enabled.

Keyboard works but wheel does not: The editor can scroll. Recheck mouse operation in another application, return focus to the source pane, and review the utility's selected action and target path.

Wheel works in some windows only: Click directly in the source pane before scrolling. Java applications can contain several child components, and the focused component receives the event first.

Mapping stopped after a Java change: Read the active Javaw.exe path again. Update the rule when the editor now launches from a different Java directory.

Other Java tools changed behavior: The assignment is attached to a shared executable. Disable the rule while those tools are active, use a utility capable of narrower application matching, or rely on PgUp/PgDn for TRI-PLC navigation.

Neither wheel nor page keys move the source: Close modal dialogs, place the caret in the editor, and reopen the custom function. Continued failure belongs to the editor or workstation input layer, not the mouse-wheel assignment alone.

Deployment and Maintenance Boundaries

An input utility becomes part of the engineering workstation configuration even though it does not change PLC logic. Document its name, version shown by the installed package, mapped executable path, selected action, and startup behavior. That record supports recovery after workstation replacement, Java reinstallation, or user-profile changes.

Test the utility under the workstation's normal user account. A rule created under another account may not be present, and a utility that is not running cannot intercept wheel events. After any desktop, Java, or TRI-PLC software change, repeat the restart and second-document tests.

The mapping affects navigation only. It does not alter source content, compile logic, transfer a program, or change controller execution. Still, verify the visible caret and selected source line before typing after a large scroll; viewport movement can reposition the engineer's attention without moving the insertion point in the same way.

Operational Recommendation

Use application-specific mapping to restore mouse-wheel navigation when rapid movement through source code is a recurring requirement. Target the active editor's exact Javaw.exe, verify both directions, restart persistence, and behavior in another Java application. Keep PgUp and PgDn as the no-dependency fallback and as the first diagnostic test.

If workstation policy blocks third-party input utilities, the keyboard method is the supported practical alternative described for custom-function editing. It removes licensing, startup, and executable-scope variables while preserving page-by-page navigation.

FAQ