Hi Ariel, > Another question: in your mails you mention an example of customizing a > menu/tool bar in the query designer/et. al., assigning a macro stored in > the DatabaseDocument basic libraries. > >> Imagine a macro configured to appear in the toolbar of a form, but >> located (as macro) in the embodying database document. > > Is this possible at all? I mean, will the window state, short cut > manager et. al. FROM ALL this modules (even does that don't have an own > UIConfigurationManager) be stored within the ODB's UIConfigurationManager?
Unfortunately, storing this configuration (toolbars, menus, keyboard shortcuts) in the odb is not possible. That's what one immediately wishes when playing with it. In OOo 2.3, you can open the customization dialogs in the query designer, but you'll notice a number of issues there: 1. When you previously had an active non-database document (say, a text document), then you are able to configure macros from this document into the designer's toolbar/etc. Of course, they don't work at all. 2. You can configure application-level macros into the designer's toolbar, but their ThisComponent variable will be pretty unpredictable. In no case, it will be the query designer (which probably would be the most reasonable thing) 3. The configuration will be stored in "OpenOffice.org Query Design", that is, all query designs will have the same customizations. 1. and 2. would be fixed with the new implementation, 3. probably not - it will be left as future task (unless we're finished too early and have too much time left :). > I mean: now you can customize a form, BUT at the module level, NOT just > for *that* form-document in particular. That's a different issue, which unfortunately just recently has been targeted to 3.x. I have this on the radar, but the implementation is in the application framework team, which is as constantly over-busy as all other teams are. > And assigning a macro inside a > DatabaseDocument to a menu item, at module level, seems to have *no > sense* although NOW you can: if you go to a form's Tools -Customize you > can add a toolbar item and assign a macro existing inside *this* form. > But this new toolbar item will be display in *every* form document, not > only in *this* form, and when you press the buttom a get script! message > will appear (what really seems to be a bug: you couldn't be allowed to > assign a macro inside a document to a module-valid element). Yes, this in fact is yet another bug in this area. In this case, it's not a database-specific bug, it also appears with other documents: You can configure a document-local macro into the module-wide UI, for all document types. I am not aware of an issue for this. If you care to submit one ;), I'd be interested in the number. Overall, I stumbled over a pretty high number of such strange bugs/behaviors, while doing this whole implementation. I'll fix some of them while passing, simply 'cause the hinder a proper implementation of the feature, but a number of them must be left for later fixing, I fear. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
