
Sender screen blanking
RGS Sender, by default, blanks the screen of the sender monitor (if one is connected) so that the desktop
session is not visible at the sender side.
IMPORTANT: Screen blanking is not supported if the sender is a virtual machine.
The default behavior is that the sender screen, with the exception of the cursor, blanks to black when you
start an RGS session. The sender screen un-blanks when the RGS session is ended.
See the following additional information about RGS Sender screen blanking:
●
There might be a delay of up to two seconds after an RGS session is started before the sender screen is
blanked.
●
If, for any reason, RGS Sender is unable to blank the sender screen, a warning dialog is displayed on the
receiver.
●
If the sender is an HP workstation, then most input from any physically-connected keyboards or mice at
the sender side is blocked while screen blanking is occurring. When RGS Sender receives keyboard or
mouse input from RGS Receiver, the sender monitor enters a power-saving mode, which blanks the
cursor as a result.
●
The Ctrl+Alt+Del key sequence is not blocked by RGS Sender for any physically connected keyboards at
the sender side. When this sequence is input into the sender using a physically-connected keyboard, the
Windows logon screen of the remote desktop is displayed at the receiver side in the RGS Receiver
window. The sender monitor remains blank while this occurs, but the monitor will exit its power-saving
mode, and sender keyboard input is not blocked until the logon screen is closed.
●
Screen blanking is supported for a Linux-based sender using multiple monitors only if NVIDIA TwinView
is in use.
●
Screen blanking can be disabled using the RGS Sender Conguration tool (see Using the RGS Sender
Conguration tool on page 57).
Input
Using touch features (Windows only, touch GUI only)
NOTE: RGS does not support touch features for Windows 7.
RGS supports the following touch features:
●
Gestures—See the table below for more information.
●
Virtual keyboard and virtual mouse—The virtual keyboard and virtual mouse can be accessed using
the RGS Receiver toolbar. The virtual mouse provides a visual indication of the remote cursor position,
which is normally not present in the touch GUI. The virtual mouse is useful when precise cursor
positioning or hovering is required.
TIP: The virtual mouse can also be enabled and disabled using the 4-nger tap gesture.
●
Hotkey sequence mapping—See Gesture (Windows touch only) on page 20 for more information.
The following table describes the gestures supported by RGS.
IMPORTANT: A press is 0.5 seconds or more, while a tap is less than 0.5 seconds.
38 Chapter 6 Using RGS features
Commentaires sur ces manuels