Skip to main content
InSource Solutions

TN - 1264 What's in an Intouch .ini?



This article from InSource is a compiled  list of parameters and their effect when placed in the INTOUCH.INI

  • Author: Mario Meza
  • Published: 06/15/2022
  • Applies to: InTouch (multiple versions)


In a standalone application, the INTOUCH.ini file is in the same folder as the InTouch application and can be modified to customize your application. For a managed application (meaning Window Maker is accessed from the IDE), the INTOUCH.ini is found in the following folders :

a) C:\Program Files (x86)\ArchestrA\Framework\FileRepository\<YourGalaxyName>\ObjectFileStorage\<YourIntouchAppName>\CheckedIn

b) C:\Program Files (x86)\ArchestrA\Framework\FileRepository\<YourGalaxyName>\ObjectFileStorage\<YourIntouchAppName>\CheckedOut

Any modification to a managed application .ini would require an update in both CheckedIn \ CheckedOut versions of the file, followed by a deploy to push any change.


  • The .ini parameters outlined in this document may not work completely as intended in your environment based on a number of factors, this could result in unintended side effects.
  • By using them, you assume FULL responsibility for the consequences.
  • They may cease to work following a product update (patch, service pack, major release) or they may not be applicable based on version / system configuration.


They are listed here as a to serve as a repository of information, its strongly recommended to thoroughly test in a sandbox before attempting to implement in a production environment.



Disable dynamic resolution by Adding this to the in the InTouch.ini file under the section [InTouch] it can help avoid resolution conversion problems. This stops Windowmaker from converting windows.. When opening the app in Windowmaker, you will still get the prompt to convert the resolution. You can click “yes” but, the resolution conversion will not occur.  

See FAQ5904



You can periodically log a value that is not changing to the Historical Log file (LGH) by adding ForceLogging=x to the InTouch.ini file, where 'x' is the number of minutes between intervals. The InTouch Users Guide states that valid values for ForceLogging are between 5 and 120.

See FAQ8234, FAQ7165, FAQ7660



Adding the line AllowPubAppEdit=1 to the InTouch.ini file may allow you to open a Published App in WindowMaker. After that, you can export the windows, do a DBDump or anything else needed. If there were ArchestrA Graphics in use, then those windows would not be able to be exported. Try entering it as the second line in the file right after the first line which has [InTouch] – If the app is listed in the InTouch Application Manager, remove it, and add it back after the .ini update using Tools/Find Applications - Then try opening it in WindowMaker



In scripting the FOR-NEXT loop time limit can be adjusted by adding an entry "LoopTimeout=X" to the INTOUCH.INI, where X is in seconds (default is 5 seconds, Increase as required.). See "Screen Updates and Performance Penalties" and "Loop Execution Time Limit" in the InTouchUG.pdf for more info.



With this entry the InTouch internal timer is changed from default 50 to ‘X’ (Increase as required). In projects with many or complex scripts in the start phase, it may be necessary to adjust this value. 



When using a blink animation, scenarios can occur when the blinking elements may be out of sync and having them blink in unison would be desired.  One suggestion would be to use a Visibility animation with a discrete tag that toggles at the desired rate however, Adding SynchronizedBlink=1 to the INTOUCH.INI can address this issue.



 TagComment comment column in the Alarm Client control is a legacy feature that came from InTouch. It uses the ‘Comment’ field from an InTouch tag for the ‘Tag Comment’ column. In Application Server, it does not work the same. For a managed application once acknowledged the alarm description is replaced with Std ACK’ because an attribute’s comment field cannot be used for the ‘Tag Comment’ column.

As a workaround:  To keep the original ‘Alarm Comment’ without updating it to ‘Std ACK - …’ : Add this entry in the [InTouch] section of the .ini SuppressRequireAckSignature=1, found in InTouch.ini in folders

a) C:\Program Files (x86)\ArchestrA\Framework\FileRepository\\ObjectFileStorage\\CheckedIn

b) C:\Program Files (x86)\ArchestrA\Framework\FileRepository\\ObjectFileStorage\\CheckedOut



Allows use of MultiMonitors with an InTouch application

See TN426 and Intouch Multi-Monitor Test Application 



The Selection Box (HALO) will default too ON, (SHOWING). By putting this .ini switch in the InTouch.ini file, the Selection Box will NOT show (HALO), meaning the halo around a push button will be disabled.



There was a design change in InTouch 10.0 which in certain scenarios caused view to freeze, meaning it could not accept any more mouse clicks or values displayed on the screen may get "stuck." Adding the flag UseLegacyOnKeyUp=1 addresses this TA147.

See also Sticky Bit Issue (ForceWriteForDiscreteIOTags=1)



Some buttons (Direct Action Push Button) may randomly maintain the value as if they were continuously pressed / fail to reset. Often coined the ‘Sticky Bit’ issue it can also affect slow changing tags. This parameter was added as a special case for instances where legacy applications had been built relying on a more immediate write from a Direct pushbutton. Instead of relying on what it remembers, by adding this, InTouch bypasses the default behavior and makes discrete writes as the action is required / happen ‘immediately’. Depending on the version of OI.CORE and OI.Server(s) there may be a few consolidated hotfixes to be applied in conjunction with this entry. 

See also (UseLegacyOnKeyUp=1)



 Opening WindowMaker / Intouch can be slow to start. Adding LoadAllActivexOnStartUp=0 under the [InTouch] sections means that the ActiveX controls are only loaded when they are opened and not when Window Maker is started. This can lead to a significantly faster start of the application. 


Resizable InputLink = 1

Resizable InputLink Width=300

Resizable InputLink Height=50

The input field of a user input animation link can be resizable to fit high resolution screen settings. The input field for the Analog and/or String user input links can be resized with the mouse pointer when there is setting in the InTouch.ini file “Resizable InputLink “ under [InTouch] section. The "Resizable InputLink" must a non-zero value for the resizable input field. After the Input field is resized the first time, WindowViewer added 2 more settings in the InTouch.ini for the width and height of the Input field dialog, and these settings can be manually changed. These values for "Resizable InputLink Width" and "Resizable InputLink Height" are in pixels. Example: [InTouch] Resizable InputLink = 1 Resizable InputLink Width=300 Resizable InputLink Height=50 



Special characters in Window names are not allowed starting with WSP2020 because of new features ( 1-3 below) which do not support special characters.

1. Web client

2. Cloud

3. Converting Native Windows to Industrial Graphic.

Legacy applications migrated to 2020 with spaces in Window Names will changed to Underscore. " _". This breaks references in scripts and other places.  

R&D has provisioned an Intouch.ini entry WindowNameWithSpecialCharacters=1

 If this entry is present, it will accept special character (Old workflow). If this entry is not there, it will NOT accept special characters(New workflow).

Note: For Industrial Graphics and cloud, the converted window names will have underscore in the place of the special character.

In WebClient, frame windows will not be displayed with special characters. If planning to use any of the newer functionalities, the suggestion is to adopt the new naming convention without the special characters.

  • Was this article helpful?