KMremoteControl - Remote Controlling Preferences
|
The Remote Controlling preferences specify various setup and behavior aspects (activation, presentation, security and networking) that apply when the system, via its keyboard and mouse, is being used to operate or "remote control" another system.
For documentation, scroll down or click in the graphic below:
- click the title-bar area (Preferences) to view a full-sized graphic containing the same clickable tabs and sections
- click an unselected tab to traverse to the documentation for that tab
- click a section within the "Remote Controlling" tab to traverse to its documentation, below

Preferences are not saved until the "OK" button is pressed. Pressing the "Cancel" button will leave the preferences unchanged.

Each preference item is saved as the change is completed.

The Activation and Presentation section specifies options that determine how remote controlling operates and the presentation of the application window:
Send Ctrl-Alt-Del to the other system by:
Pressing Ctrl-Alt-Delete: When checked, will provide an option to send Ctrl-Alt-Delete to the system being remote controlled after the Ctrl-Alt-Delete action is pressed by the user.
Pressing another key combination: When checked, allows a key combination to be entered. When used, that key combination will be translated to Ctrl-Alt-Delete before being sent to the system being remote controlled.
- Hotkey to activate and deactivate remote control: A hotkey must be defined. The hotkey is used to alternately activate, then deactivate, remote controlling another system.
Note that the hotkey is defined system-wide and, as long as the KMremoteControl application is running, will activate remote controlling from within any application.
When the cursor is placed in the entry area, entering a key or a modified key will set and show the hotkey. The Shift, Ctrl, Alt and Win(dow) key(s) can be pressed, simultaneously, with another key to create a modified key.
When the button is pressed, the following drop-down is presented:

Typing a key and/or modifiers will set and show the hotkey. The Shift, Ctrl, Opt(ion) and Cmd (i.e., command/Apple) key(s) can be pressed, simultaneously, with another key to create a modified key. Note that the modifiers and the key to be modified must be supplied as separate keystrokes. Pressing the "Done" button completes the hotkey definition. Pressing the "Clear" button clears the current entry. Pressing the "Cancel" button leaves the previously defined hotkey intact.
*Keep KMremoteControl in front, while controlling: When checked, will automatically reinstate KMremoteControl as the front application if it is switched out (using a switcher hotkey, for example). This is necessary if you use the same switcher hotkey on both the controlled and the controlling systems. For more information, see "Using Switcher and Other Hotkeys with KMremoteControl" in the ReadMe document.
**Put this application into the background when deactivating remote controlling: When checked, will cause the "KMremoteControl" application to be put into the background when deactivating the remote controlling of another system. Checking this option and the option to "Hide this application while it is in the background", will enable the hotkey to alternately "activate and show" then "deactivate and hide", which is often the preferred behavior.
**Hide this application while it is in the background: When checked, will hide the KMremoteControl application whenever it is in the background. Checking this option and the option to "Put this application into the background when deactivating remote controlling", will enable the hotkey to alternately "activate and show" then "deactivate and hide", which is often the preferred behavior.
- Allow remote controlling other systems from this system while this system is being remote controlled: When unchecked, it will not be possible to remote control another system while "this" system is being remote controlled via another system. Most installations should leave this option unchecked. Note that, while it's possible to attempt, using one system to remote control another system that is also used to remote control another system (i.e., chaining remote controllers) is not supported.
***Suppress system keys while controlling (Force Quit, Cmd-Tab switcher, Logout): When checked, will disable these keystrokes on the controlling system and allow some of them to be passed through to the system being controlled (the exact behavior is controlled by OS X).
***Blackout screen and capture hotkeys and switcher keys while controlling: When checked, will allow KMremoteControl to capture the hotkeys and switcher keystrokes on the controlling system and pass then through to the controlled system. This has the advantage that it can allow you to use the same application hotkey settings for applications on the controlling system as on the controlled system. It has the disadvantage that the controlling system's screen will be "blacked out."
Note that you can also often achieve hotkey pass-through, without the blackened screen, by defining a key substitution where the key(s) typed and the key(s) sent are the same but marked as a hotkey when defining the key substitution.
***Darken screen while controlling: When checked, will cause the screen to be darkened by an amount set via the darkening slider control. The kind of windows that will have darkening applied can be controlled via the pop-up menu.
***Make "Remote Systems Controller" & "KMremoteControl is Active" windows transparent, while controlling: When checked, will cause the "Remote Systems Controller" & "KMremoteControl is Active" windows to become transparent by an amount set via the opaqueness slider. The transparency is limited to a maximum of 95% for technical reasons dictated by OS X. This is very useful, especially when used in conjunction with other preferences, to ensure that you can see the contents of the screen on the controlling system while controlling another system.
Eliminate the use of "Metal" texturing on the applicable application windows: When checked, will use the "normal" OS X aqua window look (this documentation was generated with this option checked). An application restart is required before a change takes effect.
The Networking section specifies some options related to networking:
- Connect/sent/receive timeout: Specifies the period, in seconds, after which the failure to communicate will be considered an error. If you are working with one or more slow/busy systems and experience intermittent "disconnects" while remote controlling, increasing the timeout setting may help. It is normally best to adjust the timeouts so the communicating "Remote Controlling" and "Being Controlled" timeout settings are the same.
Technical : KMremoteControl uses a bidirectional "heartbeat" to continuously monitor the network connection status.
Enable TCP_NODELAY: When unchecked, will enable the low-level networking services to temporarily hold networking traffic in an attempt to be able to send larger packets of information. However, although this may somewhat reduce the network traffic, performance and user experience is likely to suffer severely, so unchecking this item is strongly discouraged.
Initiate searching for other controllable systems at startup: When checked, will cause the system to search for other systems to be controlled via the zero configuration mechanisms (i.e., Apple's Bonjour, originally called Rendezvous, technology) whenever KMremoteControl is started.
 
The Third-Party Mouse Driver Support section provides some capabilities that help work around problems with misbehaving mouse drivers that tend to work against KMremoteControl. These options have proven useful (i.e., are often required) for Wacom and Logitech mouse drivers. Only use these if required.
**Turn on only if using third-party mouse drivers and, on the remote controlling system, KMremoteControl switches to a different application on mouse clicks: When checked, will apply a workaround that works for some misbehaving mouse drivers. Note that using this option will increase the processor load on the remote controlling system and may adversely affect the overall responsiveness.
***Turn on only if the above option does not work: When checked, will apply a more extreme workaround that works for some misbehaving mouse drivers.
*This option is present beginning with version 1.20
**These options are present beginning with version 1.10
***These options are present beginning with version 1.50
|
|
|
|