Hi Frank,
Frank Schönheit - Sun Microsystems Germany escribió:
Hi Marc,
ThisComponent should represent the component from which it is
"triggered", the document window firing the event.
Meanwhile, I tend to this interpretation, too. The final argument
perhaps was the "ThisComponent is the same as the desktop's
CurrentComponent" from the Developer's Guide (IIRC Ariel brought this up
here).
No, it wasn't me, it was Drew :-)
For the new variable I could imagine naming it "ParentComponent" holding
the base document the definition is stored in.
Does sound
ThisComponent.ParentComponent.BasicLibraries...
reasonable?
I'd say
DatabaseDocument.BasicLibraries
Adding a new property to ThisComponent is hardly possible. Also,
"ThisComponent.Parent" already exists in today's forms, and already
denotes the database document. A dedicated variable would just make this
much more explicit and error-prove.
As you say, this already exists:
FROM the form TO the DatabaseDocument getParent() already works.
What does not exists is a [simple] way to go FROM the DatabaseDocument's
model TO the form-document's model, as we said [yeas, I know: RFE...
tomorrow I promise ;-) ]
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?
I mean: now you can customize a form, BUT at the module level, NOT just
for *that* form-document in particular. 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).
Regards
Ariel
--
Ariel Constenla-Haile
La Plata, Argentina
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.arielconstenlahaile.com.ar/ooo/
"Aus der Kriegsschule des Lebens
- Was mich nicht umbringt,
macht mich härter."
Nietzsche Götzendämmerung, Sprüche und Pfeile, 8.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
