THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 24/09/2009 at 08:36, xxxxxxxx wrote:
Tool plugins can utilize a SubDialog which is used in the A.M. instead of direct Description resources. In order to use a GeDialog, you'd need to set up the description resources in the ToolData but hide them. Then pipe the dialog settings to their counterpart descriptions so that interactive value changes are handled properly (creation of undos, calls to SetDParameter, Draw, etc.).
Piping them is your problem, of course. You can establish a 'connection' to your dialog from your tool plugins in two ways:
1. Using messages: you could use MultiMessage (might be slow) to disperse the message that will only be handled by your plugins looking for the message.
2. Direct setting/getting: Have the tool create the dialog (with unique ID!) if nonexistent and have others point to it. Then each can call methods (or access public variables) of the dialog.
Are you wanting to create a single GeDialog for all instances and types of your DescriptionToolData or one per? This will make a difference.