PLEASE DO NOT CREATE ANY MORE JDIALOGS IN PIPELINE

The DialogManager is intended to be the only way JDialogs are made. The DialogManager class has many classes for creating JDialogs under different circumstances (refer to the javadoc of DialogManager). When creating an AbstractGUI with the DialogManager it is unnecessary to add the CONTAINER or the COMPONENT to the inputs map (DialogManager takes care of that for you). However, if you desire to have only one dialog open at a time (such as when editing a parameter) you must provide the proper string to hash the dialog by. Here is my hashing convention, if it is followed then every instance which can open this particular dialog will operate correctly. In the below examples Class is the name of the GUI class that is being created.

If the dialog is independent of the activeModule then use Class.class.getName() as the hash string.
If the dialog is dependent on the activeModule then use activeModule.toString() + Class.class.getName() as the hash string.
If the dialog is editing a function then use function.toString() + Class.class.getName() as the hash string.
If the dialog is editing a module then use module.toString() + Class.class.getName() as the hash string.
If the dialog is editing a argument then use argument.toString() + Class.class.getName() as the hash string.
If the dialog is editing a class then use class.toString() + Class.class.getName() as the hash string.
If the dialog is editing a variable then use variable.toString() + Class.class.getName() as the hash string.