[MAGIC_SPECIALS] Flags (Magic xpi 3.x)
The Magic xpi configuration files (.ini files) have a number of special flags. Most of these are for Magic xpi's internal use. The flags that are relevant for the Magic xpi user are listed below. These flags are used to enhance system performance and to ensure that processes in the system are maintained properly.
|
|
|
|
CtxMaxShutdownTime=
|
Enter the number of seconds that the broker waits for active connections to terminate before forcing a shutdown. The default is 2.
This allows you to be sure that all outside processes are shut down before the Server shuts down. Processes that are linked to the Server activity can be damaged if the Server shuts down prematurely. If you need time to shut down these processes, add time to this flag.
|
|
SpecialEventQMaxInterval=
|
Enter the number of milliseconds that the current process waits before attempting to resend an event to the queue. This is done if the queue is full when a prior attempt to send the event is made. The default is 10.
This also helps fine tune the system performance.
|
|
SpecialEventQSizeLimit=
|
Type a number to indicate the maximum queue size for internal events. The default is 100.
This helps save memory consumption. Set a smaller queue limit to ensure that there are not too many activities waiting in the queue.
|
|
SpecialBeepOnRequest=
|
During Magic xpi executable module creation, beep sounds can be heard, signaling that certain modules were generated. This flag and the SpecialBeepOnWarning flag determine whether to leave the sound or turn it off. Setting this flag to N will cancel the beep.
|
|
SpecialBeepOnWarning=
|
During Magic xpi executable module creation, beep sounds can be heard, signaling that certain modules were generated. This flag and the SpecialBeepOnRequest flag determine whether to leave the sound or turn it off. Setting this flag to N will cancel the beep.
|
|
XMLDomMapper=
|
When this flag is set to N (default), the destination XML and destination IFCModel are created without loading them to a DOM. This improves the performance of the XML creation in the Data Mapper.
However, when the XML Properties dialog box's Append Data check box is selected, the above destinations will always be loaded to a DOM.
To have the destinations always load to a DOM, you need to close the Magic xpi Studio, change the XMLDomMapper value to Y, open the Studio, and rebuild the project.
|
