Custom Settings

You can easily define some global parameters for all remote access connections, regardless of the selected profile by using customSettings.js. You can find this file in the installation directory, inside the 'webrdp' folder. It is an editable javascript file that contains a global variable called customSettings. The customSettings variable uses the JSON format to define a collection of attribute/value pairs with special parameters that are not available in the profile settings. You can open it with any text editor, like notepad.

Attribute	Default value	Description
createToolbar	true	Enables the Thinfinity Remote Desktop Toolbar creation.
toolbarVisible	false	Defines the initial toolbar visibility.
checkBeforeWindowClose	true	When false, bypasses the confirmation popup triggered in the onBeforeUnload event.
noSsnDialog	false	Disables the share session popup dialog display.

This collection can be extended with any other attribute of the connect JSON parameter, except for those that are relative to the connection —user, password and computer—. When extending the collection, the overrideDefault attribute must be set to true, as specified in the Thinfinity Remote Desktop connect method reference:

// GetThinRDP(serverURL, runRemote)

// Creates a new ThinRDP instance

// serverURL: substitute with the ThinRDP server URL (http[s]://[URL - IP]:port/)

// runRemote: use to set ThinRDP mode

// -- false-> local (renders into this page)

// -- true-> remote (posts connection data to postPage ("connection.html" as default)

mythinrdp = GetThinRDP("", true);

mythinrdp.connect({

targetWindow: "rdpwindow",

centered: true,

overrideDefaults: true,

...

}

When starting a connection, Thinfinity Remote Desktop reads the values in customSettings and merges its parameter list with the profile settings, overriding the profile attributes with the customSettings variable values. Values set in the SDK connect method will also be overriden. This is a powerful tool that needs to be used carefully. Therefore, it is recommended to use customSettings.js exclusively to set these special parameters, or when you need a centralized configuration to be shared among the totality of countless profiles. Remember: defining the configuration in each profile is always safer, as well as clearer.

In conclusion, the customSettings global variable offers a way to quickly apply general custom settings that will affect all the connections.