Hello Carsten, *, Carsten Driesner wrote: > You can define a user-defined toolbar with an extension but > that must be > done using the UI configuration API. This is not an easy way > to create > toolbars and I don't see any benefit for you to use a user-defined > instead of an add-on toolbar (there is one exception as user-defined > toolbars can be configured by a user, add-on toolbars not).
Oh, i think the problem is only my word "user-defined"? In this case: "user-defined" was only my word for a 'normal' toolbar (for example: a toolbar which is defined automatically bei the BasicAddOnBuilder (from Paolo Mantovani)), not for a special kind of toolbar > You can > influence the visibility of an add-on toolbar via separate > <Module>WindowState.xcu files. There is one thing you have to keep in > mind and that many people miss when they provide configuration files > within their extension. The configuration uses different layers with > priorities, that means the user-layer always have the highest > priority > and settings there overrule settings in the extension and > shared layer. i understand > I think in your case is a CalcWindowState.xcu file in your user-layer > which defines your add-on toolbar as visible. Just remove the whole > CalcWindowState.xcu file and try again. Yes you are right, that works for me. greetings, Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
