Sven, 2005/8/29, Victoria, Sven <[EMAIL PROTECTED]>: > > Note that I declared otxtfield of type Variant, not of type Object > > because there are some rare situations where it would fail declaring a > > variable of type Object. > > ? > Can you give more insight on this matter?
I have never actually used Dim x as Object so I have no experience on unexpected results. The Developer's Guide talks about prefering Variant over Object so I just went that way not investigating on that matter. > Doc = StarDesktop.CurrentComponent > So Doc is a document ... ok ... but what can I do with a document? > [...] > Surely there must be more to a document than only these methods? > But how do can I find this information from this point on? Sure there is, the thing is that the Starbasic interpreter takes a lot of work away from you, as do other scripting interpreters. The Basic engine actually binds all exported interfaces your referenced object to it (behind the scenes). That's why you don't need to use queryInterface calls that can frequently be seen in Java/C++ code, in order to invoke a method. > It would be really nice if on the the api page of OfficeDocument > (or XComponent) references to subclasses (or implementations) are included. It has! Click on the "Use" link that appears for every idl object at the top. At some places the lists are not complete, so if you find an interface that can be accessed from a certain object and its not listed there, just file an issue for it. > I guess that the Variant construction is the way to go :( There is nothing sad about it, if you choose well-named identifiers, Starbasic should be one of the easiest programming languages to read (+ understand) in my eyes. -- Best Regards Christian Junker --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
