Starting an Extension on Startup

[Bernhard Reiter]

On Monday 20 November 2006 22:52, George wrote:
> What I'm hoping to achieve is that as soon as Thuban is opened a dialog
> box will be raised by the extension prompting the user to "login". 

With an event driven application like Thuban, are you sure that this is
the right behaviour? I mean, what if the user this time wanted to do something
else with Thuban, like open a simple shapefile or another Thuban session?
A dialog box that always comes up might block other tasks.

> The extension will then be used to do populate a database with information
> about existing features and (probably) do some digitisation.
>
> I understand that extensions get executed when they're imported and that
> I can initialise things in there however I'm not sure how I can start
> displaying dialogs unless I know what the parent window is, which would
> come from the context object which isn't present when the extension is
> imported?

If you require this, we could add a hook for extentions to get called 
at a place when the windows are open and before we go into the main 
event loop. Then your extension can hook in there and pop up a dialog.

So where would you open a dialog box, if you could directly do it 
in Thuban's main code? :)

Bernhard
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.intevation.de/pipermail/thuban-devel/attachments/20061121/5c60f9dd/attachment.bin