![]() |
||
This tab deals with the options concerning: | ||
User Interface Style |
||
![]() |
||
|
||
Data SaveNote that the "No automatic backup" and "Incremental backup" options are available only for CATIA. |
||
![]() |
||
Automatic backup every ... minutesIf this option is selected, it means that you can specify a save frequency other than the default frequency (30 minutes). This option is activated by default. The purpose of this option is to automatically save your data to allow you to recover it after a crash. When a crash occurs, and you restart your session, the Warm Start dialog box asks the following question:
If you choose "Yes", your documents will be recovered in the state in which they were last saved by the automatic save option. Any data created after the last automatic save will not be restored. If you choose "No", a new document will be created when opening the session. |
||
![]() |
You may encounter,
when working on a document, a dialog box containing the following message:
When this occurs, we recommend that you click OK to continue (a check is launched on your data in the background). Then, you should immediately save your document(s) and exit then restart your session. We also recommend the same method if a dialog box appears containing the
message:
|
|
Disconnection |
||
![]() |
||
Automatic disconnection after ... minutesIf this option is selected, it means that you activate automatic disconnection of your Version 5 session after a user-defined duration (in minutes) without program use. Note that once the disconnection time is reached, the session exits gracefully with no warning because the end user is not supposed to be in front of the screen since the disconnection is only supposed to occur when interactions have taken place. Because there is no warning message before exiting the session, make sure you have saved your work well in advance. When a data backup is triggered, it behaves with regard to CATIA disconnection like any other standard interaction being processed. The disconnection manager:
|
||
Referenced Documents |
||
![]() |
||
Load referenced documentsIf this option is selected, it means that when a father document is
loaded, the child documents it points to are also loaded. However, if you
clear this option, only the father document is actually loaded when you
open it. This may be useful for reasons of performance and efficiency. A
typical case of this is a CATProduct or CATDrawing document, i.e. the
father document pointing to CATPart or model documents i.e. the child
documents. Additional examples may include a CATProcess document (i.e.
parent document) pointing to a CATProduct document (child Once a father document has been loaded you cannot load or unload its child documents as changing the option cannot apply retroactively. You must close the father document, select or deselect the Load referenced documents option then reopen the father document. If you open a father document containing unloaded child documents you can load one or more of these documents using File > Desk (see Using the FileDesk Workbench). |
||
Note that when
loading objects pasted As Result With Link or external
references, the pointed documents containing the referenced geometry are
not loaded and this, even if the Load
referenced documents option is activated. These pointed
documents are identified by the symbol
![]() |
||
Note also that even
if the Load referenced documents
option is not activated, the geometry is still loaded when reopening a file
containing a .model document.
|
||
Conferencing |
||
![]() |
||
Conference driverIf you installed a license for a DMU Navigator product, you will be able to run conferencing sessions: a conference host initiates a conferences and invites other users to join the conference as guests. The actions replicated during a conference are the following:
Conferencing is available on the Windows and UNIX platforms, and is based on two underlying prerequisites:
For more information, refer to the Version 5 - DMU Navigator User's Guide. |
||
Drag and Drop |
||
![]() |
||
Enable Drag and Drop for Cut, Copy, Paste UseIf this option is selected, it means that dragging and dropping in the viewers (for copying, pasting or cutting purpose only) is enabled. For more information, refer to Dragging and Dropping Icons onto Objects and Dragging and Dropping Objects onto Objects in this guide. Note: this drag and drop option does not apply to toolbar customization.
|
||
Memory Warning |
||
![]() |
||
Trigger memory warning at ... % of memory useThis option helps you to save your data before a crash occurs due to excessive memory use. A warning popup when the process memory use exceeds a certain percentage of the address space usage or when the remaining free memory fragmentation reach a certain threshold. This popup warns you that because the amount of remaining memory is becoming low, you should save your data and exit the session: Important remark: this warning does not concern RAM memory use or paging space use. It is not dependant on the computer resources, only on the process address space as we consider that, in general, in a typical environment and with a recommended configuration, the 32-bit address space is the limiting factor in terms of memory consumption. Check this option and set the percentage of address space indicating when to trigger the warning. This will set the limit value for address space use and fragmentation. The thresholds may be changed but it is not advisable, except for expert users. Once the warning is generated, the warning in itself should not crash or freeze your session. Note: Please note that on 64 bits, the address space size is huge. With current existing hardware (physical resource), the threshold of warning generation cannot be obtained. Therefore this warning will not be triggered on 64-bit platforms on currently available computers. However, the mechanism is kept for the future in case computer hardware evolves over in the next year. Limitations
|
||
Additional Information Added to Session and Abend TracesWhen the memory warning mechanism is activated, additional information is added to the Session_Information_File and in abend traces to help in investigating certain memory crashes. By logging this information, added information allows the segregation of scenarios involving crashes which occur due to full memory consumption. So it will now be possible to distinguish between:
As perceived by the end user, application behavior does not change. However, if the memory warning mechanism is activated, and if a warning is generated during the session, extra information is logged in the SessionInformationFile indicating that a warning was generated. Later, if the application crashes, the same information is logged in the AbendTrace associated with the crash. Here is a sample of the type of information added (with the value set to 1% simply for the purpose of illustration):
The information contains:
|
||