Download GME Manual and User Guide - ISIS Forge

GME Manual and User Guide
Figure 18. Connection customization horizontal/vertical edge snap threshold value
settings
GME tries to obtain the data of an auto-routed connection path and feed that edge information into the fully
customizable path's data. That work is done by a special algorithm: it converts the route determined by the
auto-router logic into a series of fully customizable connection points. This way you can start to customize
an existing line and do not have to build up one from scratch. This algorithm runs before you change the
auto routing state of the GME application, on a whole model or an individual connection. Note that this
algorithm needs to run the auto-routing algorithm on the whole model to be able to obtain the needed
information, so it might make opening or refreshing of a model view slower. For example if you modify
the auto-routing state of a sub-model and you open that sub-model in a view much later, the conversion
algorithm will run only at the time (during the view opening procedure).
The start and the end points of the connections are special: they are still determined by the auto-routing
logic. This is partly because connection path ending in a port wouldn't be movable anyway because the
location of the port cannot be changed inside the model box (the port position is automatically computed
and fixed).
4.10. Emergency saves and GME CrashDumps
GME is able to generate a CrashDump in the event of a GME crash. A CrashDump file (a Microsoft
MiniDump crash report file with additional custom information stream) contains a collection of
information related to the particular crash. With the help of this file, developers have information to analyze
the crash and discover the bug more easily. The file has a dmp extension and named after the precise
date and time (GMT) of the crash event and the process Id and thread Id of GME. This should result
in a unique name of the form: "GME_CrashDump-yyyy-mm-dd_(hh-mm-ss)_pid_tid.dmp", for example:
"GME_CrashDump-2009-10-01_(16-09-56)_3180_4828.dmp".
32