try that http://www.pitonyak.org/AndrewMacro.odt
you find that part in "Listing 5.47: Setting document variables." p 56ff
Not The book but the Andrews free-doc !
I learned that there are also MasterFields and that Fieldmaster.User can
be used for storing hidden stuff
Thanks a lot
Fernan
>>
>> hi harald,
>>
>> i want to insert a field and add some properties which are not
>> supported by
>> the default field-elements of OOo.
>> this properties must be stored in document.
>> i store these properties in invisible document vaiables, like it's
>> described
>> in andrew pontyaks macro
Harald Weyhing wrote:
Jan Füssel schrieb:
Hi Jan,
what do you excatly want to do? can you give a quick usage scenario?
I am not really sure what you are trying to do.
Cheers
Harald
-
To unsubscribe, e-mail: [EMAIL PROTECT
Hi Jan,
why don't you use a naming konvention like: name your invisible
variables like ? This way the
placeholder name would act as ID.
Cheers
Harald
hi,
if you take the prior example, it is possible to have more than one field
with the placeholderfieldname == surname.
for example the issu
Jan Füssel schrieb:
Hi Jan,
what do you excatly want to do? can you give a quick usage scenario?
I am not really sure what you are trying to do.
Cheers
Harald
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comm
Hi Jan,
what do you excatly want to do? can you give a quick usage scenario?
I am not really sure what you are trying to do.
Cheers
Harald
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
Jan Füssel schrieb:
Hi Jan,
in content.xml of a document containing placeholders you will find an
attribute "text:description" in every placeholder:
you can define this description in the dialog while creating the
placeholder. I don't know how you can get this information through th
Hi Jan,
in content.xml of a document containing placeholders you will find an
attribute "text:description" in every placeholder:
you can define this description in the dialog while creating the
placeholder. I don't know how you can get this information through the
API but I would bet
Hi Jan,
in content.xml of a document containing placeholders you will find an
attribute "text:description" in every placeholder:
text:description="reference1">
you can define this description in the dialog while creating the
placeholder. I don't know how you can get this information
This service seems to be an "internal" service that is not
instantiatable without a certain context. I assume that you can
instantiate it only with the XMultiServiceFactory interface of a text
document, but not from the general service manager you either received
or bootstrapped. Such services ver
Jan Füssel wrote:
> I don't want a second service with an equal name. i need a component, that
> has the same functionality like the other fields in OOo. In other words: i
> want an own component, which i can insert in an textdoc via the
> "insertTextContent"-method out of a basic macro. this comp
Hi
Jan Füssel wrote:
I don't want a second service with an equal name. i need a component,
that
has the same functionality like the other fields in OOo. In other
words: i
want an own component, which i can insert in an textdoc via the
"insertTextContent"-method out of a basic macro. this compon
Jan Füssel wrote:
> Hi,
>
> i have a question about the uno api. is it possible to extend an existing
> service via an own uno component?
> in my case, i want to add some special functions to the service "
> com.sun.star.text.textfield.Macro ".
> the new service should delegate all default calls
I don't want a second service with an equal name. i need a component, that
has the same functionality like the other fields in OOo. In other words: i
want an own component, which i can insert in an textdoc via the
"insertTextContent"-method out of a basic macro. this component has a few
more appli
Jan Füssel wrote:
Hi,
i have a question about the uno api. is it possible to extend an existing
service via an own uno component?
in my case, i want to add some special functions to the service "
com.sun.star.text.textfield.Macro ".
the new service should delegate all default calls to "original"
Hi,
i have a question about the uno api. is it possible to extend an existing
service via an own uno component?
in my case, i want to add some special functions to the service "
com.sun.star.text.textfield.Macro ".
the new service should delegate all default calls to "original" service.
i have tr
16 matches
Mail list logo
