Am Sonntag, den 16.12.2007, 22:51 +0100 schrieb Frank Schönheit - Sun
Microsystems Germany:
> Hi Marc,
>
> > I could imagine some other very useful shortcuts especially - - but not
> > only - for base:
> >
> > - get a list of open documents (without going throught the desktop
> > discriminating other doc types - not easy when having forms and writer
> > docs, I think)
>
> Item 1: Ever tried the TDOC UCP? If you do not know it, to get an idea:
> Open a few documents, open the (internal!) File Open Dialog, and enter
> "vnd.sun.star.tdoc:/" in the file URL box, press OK. So far for "through
> the desktop" :)
> Item 2: The module identifier is what best serves document
> discrimination: Writer, Reports, and Forms have different module
> identifiers (XModule::getIdentifier)
No, never. I'll evaluate. :)
> > e.g. aBaseDoc.Components().getByIndex()/.getByName()
>
> As said in my response to Ariel: Yes, but that's a different topic.
Okay.
> > - get access to the four sections of a base doc container: tables,
> > queries, forms and reports (although that should be easy doable as it is
> > now ... lacking time to search and test)
> > e.g. aBaseDoc.Forms() (doesn't this exeist already?)
>
> Hmm - what exactly do you want to access here? The UI? That's the
> selection supplier, I suppose. The component definitions? That already
> exists. The open "sub documents"? That doesn't exist, and is the same as
> you mentioned above.
The UI and the component definitons, yes.
> I'm unclear what you exactly mean here, please elaborate.
Me too, that apparently was a shot into the blue. But you get the idea,
I hope. ;)
> >> Imagine a macro configured to appear in the toolbar of a form, but
> >> located (as macro) in the embodying database document. You want to
> >> execute this macro from within the form, perhaps from within the
> >> database document, and surely from within the Basic IDE during
> >> developing it.
> >> What's your expectations how ThisComponent should behave?
> >
> > Do I understand right: the base container doc is a component and each
> > su-document contained is loaded as such when openened?
Without having read much of the other answers:
ThisComponent should represent the component from which it is
"triggered", the document window firing the event.
Anything else would break the concept used now. If using ThisComponent
from the BASIC IDE I'm trained to activate the "working window" once and
then run the macro. A change here would be very confusing.
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?
Marc
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
