Christoph Lutz wrote: Hi Christoph,
thank you for the example code. It works very well. I would like to mention a behaviour I just noticed: the new created popupmenu will not be restored after an restart of OOo, so there is no persistence like described in your code comment... But I asume it was your intention not to call the oModuleCfgMgr.store() method after the line " oModuleCfgMgr.replaceSettings( sMenuBar, oMenuBarSettings )"? For my tests, I added the respective line to your example-code.
Your are right I forgot to add the oModuleCfgMgr.store() call.
But now to my question: I translated your example to java (I tried to do an exaxt one-to-one-translation of your basic-example) and the java-code bahaves slightly differt from the basic code: In basic, the popupmenu and all elements are visible directly after calling the code. Using my java-code, the popupmenu is created, but the element(s) in the popupmenu are not visible. The strange thing is, that after the call of oModuleCfgMgr.store() and a restart of OOo, the popupmenu and all its previously unvisible item(s) get visible. Do you have got an idea, why the items are not visible directly after creation, while the same code in basic creates visible items? I think this might be a bug...
I looked over your example and I cannot see an obviously problem. Please give some days to check wants wrong here. I will let you know when I have more information. It's possible that this might be a bug, although OOo only uses this API internally for customization.
Regards, Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
