> For the complete documentation index, see [llms.txt](https://doc.sysdevmobile.com/kalipso/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.sysdevmobile.com/kalipso/documentation/project/properties/advanced.md).

# Advanced

<figure><img src="https://1614058754-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJ5vDGuBZwhJDeu5Rq7Wt%2Fuploads%2Fgit-blob-55abaf33f9d6ebd9dd9a7186aecfe77dcae56294%2Fproject_properties_others_6.png?alt=media" alt=""><figcaption></figcaption></figure>

* **MIS Product Code** - This is the product code used by Kalipso to identify to MISCommunicator. In MISCommunicator this is defined under the "Products" button.
* **Keywords Scope -** *This option is for keywords ERRORCODE, ERRORMSG, IERRORCODE, RECORDCOUNT and POPUP.*
  * “Global” - It means that this keywords work has global variables, their value is equal in all project
  * “Event” - It means that this keywords work has temporary variables, their value is only valid on the event that is running. If for example an ActionSet is called these keywords will have their own value inside the actionset that is running.
* **Custom URI Schemes -** Names through which your application can be launched like a protocol.
* **Soap Prefix** - Add a specific SOAP Prefix to your project.
* **Preload Control's Images in Memory (win32 only) -** *“Does what it says” .* The pre-loading will be executed when the Form is open. If checked, this option will slow down the opening of the Form and will have a higher cost of memory but the display of images in the Controls will be faster.
* **Manage Key Event On** - When defining a Key Event, that Key event can be triggered either at Key Down or Key Up. With this parameter, you can define if you want the Key Events to be triggered when the key is pressed, released or both. Notice that if defined both "Key Down" and "Key Up", each Key Event will be triggered twice for each keystroke.
* **Override default Keyboard handler for mapped Key Events** - By choosing this option you can override the default behavior of a key on an input control, or on a form. When you add an event associated with a key, when that key is pressed the code you have on that event is executed, but the default behavior for that key is also executed. For example, on a text box it is possible the add an event for the key "1". So if the user presses the key "1" the number "1" is entered into that text box and your code is also executed. If you enable this option, when the key "1" is pressed, nothing is sent to that text box, only your code is executed.

  * No
  * Yes for Controls
  * Yes for Controls and Forms

  This option is only for Android and Win32.<br>
* **Android code execution mode -** In Android, if a specific set of code is executed in the user interface thread for longer than 4 or 5 seconds, a message will appear to the user saying the application is "non responsive" (ANR) and it allows the user to kill the application.\
  \
  The advantage of "Background Thread" mode is that the "ANR" message will never appear to the user, but if the application makes a lot of changes to the user interface in the code, it can be slower. For application that don't have code running for long periods of time, the "User Interface Thread" mode is normally preferred, and if a specific function requires a lot of time to execute it can still be executed in a background thread by specifying "Thread Mode" = Yes in the "Execute Action Set" actions.

**Paths**

* **Documentation** - Folder where Kalipso generates the documentation of the Project.
* **User Backups** - Folder where Kalipso saves the backups of the Project.