Register Problem types

Menu: Help->Register Problem type...

In the same way that some of GiD's capabilities have restricted access before it is registered, so not all problem types are available without registration. The layout of the Register Problem type window is shown below:

Problem type register window

If a problem type has been registered previously, the password can be reloaded by clicking
and selecting the folder where the old password is.

A problem type does not need to be loaded to be registered. In this case, click the Choose a Problem type bar and a window similar to the one below will appear where you can choose a set of problem types to be registered. If a problem type is currently in use then it is selected by default.

Choose Problem type window

The "Register from file..." menu, will ask the user for a .pwd text filename, that contain one line for each problemtype or GiD to be registered. It's interesting to register several modules, and GiD in a single step.

The contents of a passwordfile.pwd can be something like this:

machinename password # yyyy mm dd Password for module 'RamSeries5.4/ramsolid.gid'

machinename password # yyyy mm dd Password for module 'kratos.gid'

machinename password # GiD 8

instead 'machinename' and 'password', for floating licences the server IP must be provided

Customizing Problem type registration

GiD provides a default validation when registering a module or problem type. This consists of checking that the password is not empty. If the password is valid, GiD appends a line to the file <problem type>/password.txt similar to this:

hostname password # 2008 01 19 Password for Problem type '/pathroot-to-problem-type/problemtype.gid'

This default validation can be overridden, but this involves Tcl programming. For a description of how to provide a custom password validation see ValidatePassword node from Customization Manual.