office-gobmx/dbaccess/source
Frank Schoenheit [fs] 538e41ebb4 autorecovery: form and report wizzard now also using XDatabaseDocumentUI, instead of manipulating document definitions
All database object wizards by now employ XDatabaseDocumentUI. This way, it is ensured that the controller
has the full control over the opened sub components.

Still, other third-party code could use direct access to the document definitions, and open sub documents this way.
This would go unnoticed by the application controller at the moment. I would be possible to fix this, by introducing
broadcasts from the document definitions, listened to by the controller. But as this sounds like a rare case, and
XDatabaseDocumentUI is the preferred way for third-party components, too, such an implementation is deferred to Later ...
2010-02-04 16:04:06 +01:00
..
core autorecovery: form and report wizzard now also using XDatabaseDocumentUI, instead of manipulating document definitions 2010-02-04 16:04:06 +01:00
ext merge with db33a 2009-12-02 13:40:39 +01:00
filter autorecovery: more sophisticated configuration data for interaction handlers 2010-02-01 21:32:33 +01:00
inc autorecovery: more sophisticated configuration data for interaction handlers 2010-02-01 21:32:33 +01:00
sdbtools #i103496#: split svtools; improve ConfitItems 2009-10-16 00:05:16 +02:00
shared CWS-TOOLING: integrate CWS dba32c 2009-07-03 14:21:50 +00:00
ui autorecovery: form and report wizzard now also using XDatabaseDocumentUI, instead of manipulating document definitions 2010-02-04 16:04:06 +01:00