On 04/24/2015 03:31 AM, Jeff Hooker wrote:
I have 3 custom right-click menus defined, each in its own
configuration, each defined with the
<commandname="{contextualMenuItems}extraMenuItems"> command.
When I create a new document from each of the different configurations,
the right-click menu for all three documents will be the right-click
menu for whichever document I created last.
That's normal because commands are global to all configurations. Hence
the last loaded command "{contextualMenuItems}extraMenuItems" overrides
the previously loaded one.
Note that you the local part "extraMenuItems" is not significant. You
can call it whatever you want. This means that you can have
"extraMenuItems1", "extraMenuItems2", "extraMenuItems3" to prevent one
command to override the other.
I have tried making the menus more specific, using the
<commandname="{Config Name contextualMenuItems}extraMenuItems">
variant of the command, but it makes no difference to the outcome;
whichever configuration was last used to create a new document (or open
an existing document) the right-click menu will be the menu that appears
across all the open documents.
I’m running version 6.0.0 with the included JVM on a Windows 8.1 machine.
Thoughts?
Well, we use this mechanism in the stock configurations and we don't
experience this behaviour.
Note the use of the "$c" variable. More info at the very end of this email.
XXE_install_dir/addon/config/dita/topic.xxe
---
<command name="{$c contextualMenuItems}imageMenuItems">
<macro>
<sequence>
<match context="$selectedElement" pattern="image[@href]" />
<command name="{dita}imageMenuItems1" />
</sequence>
</macro>
</command>
<command name="{dita}imageMenuItems1">
<menu>
<item label="Set Image..."
command="setObject" parameter="href anyURI" />
<item label="Copy Image" command="copyImage" />
</menu>
</command>
---
XXE_install_dir/addon/config/docbook5/docbook5_support_base.incl
---
<command name="{$c contextualMenuItems}imageMenuItems">
<macro>
<choice>
<sequence>
<match context="$selectedElement"
pattern="db:imagedata[@fileref]" />
<command name="{db5}imageMenuItems1" />
</sequence>
<sequence>
<match context="$selectedElement"
pattern="db:imagedata[./svg:svg]" />
<command name="{db5}imageMenuItems2" />
</sequence>
</choice>
</macro>
</command>
<command name="{db5}imageMenuItems1">
<menu>
<item label="Set Image..."
command="setObject" parameter="fileref anyURI" />
<item label="Copy Image" command="copyImage" />
</menu>
</command>
<command name="{db5}imageMenuItems2">
<menu>
<item label="Set Image..." command="{db5}setSVG" />
<item label="Copy Image" command="copyImage" />
</menu>
</command>
<command name="{db5}setSVG">
<macro>
<sequence>
<test context="$selectedElement" expression="is-editable()" />
<set variable="selectedElement" context="$selectedElement"
expression="./svg:svg" />
<command name="setObject" parameter="- XML" />
</sequence>
</macro>
</command>
---
Note that above, "$c" is an alias for the name of the configuration
where the command has been defined.
If the command "{$c}foo" is defined in common.incl and if common.incl is
included in config1.xxe, config2.xxe and config3.xxe, then this will
create 3 different commands "{config1}foo", "{config2}foo" and
"{config3}foo".
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
