|
The Save-tab contains the Save-table where cursor customizations are saved. Saved customizations can be recalled
using the keyboard
or through the Save-table. To save a customization, the customization is first defined in the Cursor-tab and then
saved using the Save-button. Up to 256 saves are possible and non-English save names may be used. The special save
name of {Startup cursor} can be used if a specific customization is needed at the start of CursorNode. If the
special name is not present, then CursorNode will start with the customization that was active in the last session.
- Save name. Input a name to use for saving a customization. If the save name already exists, then the existing save will be overwritten.
- Marker for focused row in the save table. Clicking anywhere in a row places the marker in that row.
- A save table row. Click anywhere on the row to recall customization saved in that row.
- Recall key menu. Optionally select a recall key to save with a customization. If the recall key is already used by an existing save, the key will be removed from the existing save on committing the new save.
- Save button for saving the currently active cursor customization.
- Eject button for deleting the focused table row.
- Save table, supports 256 rows.
- Saved recall key. Hold down [CursorNode Hotkey] and press the Recall-key to recall the associated cursor customization.
The Tags-tab contains the Tags-table used for identifying individually customizable cursors. The identification
data are used in Cursor-sets. The table is first cleared and then incrementally filled by CursorNode when tagging
mode is enabled.
|
- Tag symbol. For examples, tag symbol '01' corresponds to this tag shown on screen:
- Visual ID of cursor being tagged. The ID is calculated from the visual appearance of the cursor.
If the bitmap data of the cursor changes, for example from software update, its ID will also change.
- Marker for focused table row. Clicking anywhere in a row places the marker in that row.
- Copy button. For copying ID and Name in the focused row for pasting into a Cursor-set definition.
- Special illustration row for the OS arrow cursor. OS cursors have static visual ID's that correspond
directly to how their tags look. These are not added to the table to reduce clutter.
- User-entered or default name for the tagged cursor. Click to change.
- Name field of the focused row. Optionally, click to enter a name for the tagged cursor. This helps
remembering which visual ID is for which cursor when many cursors are involved.
- Tagging mode status
Tagging mode
The tagging mode is toggled on and off using [CursorNode Hotkey] [Return]. This is a special mode in CursorNode that enables
identification of customizable cursors. The identified cursors can then be selectively targeted for customization
in Cursor-sets. This style of customization is more appropriate for many scenarios compared to the default
broad-brush approach used by CursorNode. While in tagging mode, cursor customization is disabled.
During tagging, the cursor on screen is replaced with a tag. The tag is just a special cursor used in the tagging
mode. The tag signifies a cursor has been tagged (identified) at that screen location and its visual ID has been
added to the tags-table. As the cursor is moved on the screen, cursors with different appearances are given other
tags. Tags are bound to cursors in order of cursor discovery. The tag is removed from screen when the tagging
mode is exited.
Enter tagging mode
- Game/app window
- Game/app cursor
- Tag that has tagged the game/app cursor. On showing the tag, the visual ID of the game/app cursor is added to the tags-table.
Pressing [CursorNode Hotkey] in the tagging mode toggles between displaying the tag and the cursor it tags.
This provides a quick way for the user to work out which tag has been associated with which cursor visual ID
when looking at the tags-table.
[Hotkey]
[Hotkey]
- Game/app window
- Tag
- Game/app cursor tagged by the tag
Tagging for UWP
UWP programs are structured differently to conventional programs. For this reason, tagging works
differently for UWP programs. Unlike for conventional programs, tagging can only be enabled for one UWP
program per tagging session. A session comprises of: 1) entering tagging mode; 2) optionally tagging
some cursors; 3) exiting tagging mode. To enable tagging for a UWP game/app, the tagging mode must be
entered with the cursor directly over some part of the UWP program window. Although, the program needn't
have focus. Upon entering the tagging mode for a UWP program, the mode is also entered for all
conventional programs that CursorNode is able to work with.
In most situations when working with a UWP program, the program must have focus for all the described
visual effects to take place.
Tags
Tag |
Tagged cursor visual ID |
Description |
... |
Various numerical |
For tagging program-specific and uncommon OS cursors in conventional programs |
|
None |
Shown in two situations. 1: Awaiting cursor discovery - move cursor to begin. 2: Cannot tag cursor at the tag location because all available tags are used. |
... |
Various numerical prefixed with 'U' |
For tagging program-specific and uncommon OS cursors in a UWP program. Shown when the UWP program has focus. |
|
None |
Shown when the tag is over a focused UWP program that doesn't have tagging mode enabled |
|
ARW |
For tagging the OS arrow |
|
HND |
For tagging the OS hand cursor |
|
HEI |
For tagging the OS north-south window resize cursor |
|
NE |
For tagging the OS north-east south-west window resize cursor |
|
NW |
For tagging the OS north-west south-east window resize cursor |
|
PRO |
For tagging the OS arrow with small hourglass cursor |
|
SIZ |
For tagging the OS north-south west-east window resize cursor |
|
TXT |
For tagging the text I-beam resize cursor |
|
WAI |
For tagging the OS hourglass cursor |
|
WID |
For tagging the OS west-east window resize cursor |
|
|