Global Event Macros

[gcrews]

When I put the following code in xmetal.mcr it does not get run when I change view. I suspect this is because there is already a macro in the topic_ditabase.mcr , Is there any way to make a global event macro that applies to all types and not have to edit every single mcr for each type?
<MACRO name="On_View_Change" lang="JScript"><![CDATA[
test();
function test()
{
   Application.Alert("Hello World");
}
]]></MACRO>

Another thing, Is there a way to get Xmetal to reload a document when you open the file and it is already open?

[Derek Read]

I'll have to investigate the conflict you seem to be having, I think your suspicion is probably correct however.

You can reload a document using the Reload() method.

[gcrews]

When I try to use ActiveDocument.Reload() on a DITA document,  Xmetal pops up the dialog asking for a dtd. 

[Derek Read]

I'm not sure why this would occur for DITA documents but I suspect it is because we have some logic in the DITA functionality that does some fancy catalog lookups or it might be part of the redirection code we use when checking to see where a document should open (topic vs map with a decision to open maps in the Map Editor or Tags On / Normal view).

Why do you need to do a reload? Perhaps knowing that will let me figure out another means. Note that customizing the DITA functionality is not supported so there may not be any supported way to do what you want to do.

[gcrews]

With a fresh install of Xmetal 6.0.1.030 , on the reviewer sample document it still asks me for the DTD on ActiveDocument.Reload(); . I tried the macro in the application level macros and document type level, both locations cause the same issue.

<MACRO name="Macro Name" key="~" lang="jScript"><![CDATA[
ActiveDocument.Reload();
]]></MACRO>

[gcrews]

can anyone verify this? it sure would be nice to be able to reload the document though macros automatically on demand.

[Derek Read]

Yes, I have verified it (the issue occurs). I think what you're looking for is a quick fix. That I don't have.

If you can answer the question about why you need to do this I can communicate that to the development team and we might be able to figure something out. In addition, knowing that will allow us to build requirements into the DITA functionality that are currently missing.