Pages: 1 2 3 4 5 6 7 8 9 10
 on: January 22, 2018, 03:25:17 PM 
Started by lerche - Last post by Derek Read
Any MCR file you place in the Startup folder is Application-level (available before any documents are open and for every document type).

 on: January 21, 2018, 03:12:47 PM 
Started by lerche - Last post by lerche
Thank you very much for your answer!

It's a great pity, but it is good to know. What would you suggest for writing a global macro that can analyse the content for several kinds of XML documents? I think the only way is to write a macro for a specific dtd. After that i would deploy the resulting macro in the startup folder. Are there any other good options?

 on: January 19, 2018, 08:03:09 PM 
Started by lerche - Last post by Derek Read
This is a known limitation. It is documented in the readme for XMetaL Developer as "Application-level XAC debugging does not work".

You will need to deploy the MCR file in this case, and if you need to debug it you can insert a debugger statement into the file at the location you want to trigger script debugging. It isn't as elegant as being able to start it from Visual Studio with the ability to set a break point but it should give you script debugging.

For JScript insert the keyword "debugger" (without quotes) at the line you wish to trigger the debugger.

 on: January 18, 2018, 04:35:06 PM 
Started by MichaelLohr - Last post by XMetaLOldTimer
Hi Michael,

When you add a project reference to the XMAX dll, Visual Studio should auto-generate these two dlls.  You can search the project directory to see if the Ax...dll is there.  If the Ax….dll is not generated, you can use aximp.exe to generate it.  Generally, it is recommended to delete these two project references prior to reimporting the reference to a newer version of the XMAX dll (or any other COM dll).

Beyond the information provided above, we recommend searching Visual Studio forums for more help.  Here are few links I found while researching your question:


 on: January 18, 2018, 02:50:03 PM 
Started by lerche - Last post by lerche

First of all: Thank you Derek Read for activating my profile on this board.

My Question relates to the following system:

XMetaL(R) Author Enterprise
XMetaL(R) Developer Version
Visual Studio 2015 (Community Edition) Update 3
OS: Windows 10 Pro, English

I am new to XMetaL Developer and I plan a small Application Customization for XMetaL Author Enterprise with my Experience in JavaScript. Therefor I created a new project with Visual Studio and tried to write a simple 'Hello World' program by testing different events like

  • On_Application_Open
  • On_Application_Close or
  • On_Update_UI

When I start the program out of Visual Studio by pressing the 'Start' button, it is strange that the code will not be executed. By creating a breakpoint in the line
Application.Alert('Hello world');

I can see that the breakpoint would not be hit. You can see it by the red circle with the white filling (have a look at attachment). But when I copy the build artifact (*.mcr file) into the startUp folder (C:\Program Files\XMetaL 12.0\Author\StartUp), the code will be executed. I know it, because I can the see my 'Hello World' alert boxes.

Is this problem a bug of XMetaL Developer or am I doing something wrong?

I would be grateful for your help.


 on: January 17, 2018, 04:41:58 AM 
Started by MichaelLohr - Last post by MichaelLohr
Hi Derek,

I'm new to the XMAX development and try to update our existing application from "XMAX 10" to "XMAX 12".

We have a C# client application where the XMAX control is used inside.

In VisualStudio we have currently the following two references:
* Interop.XMetaLControlLib
* AxInterop.XMetaLControlLib

I can renew the first reference by making an reference to the "XMetaL XMAX 12.0 Type Library" in the "COM"-category,
but I do not know who to update the second one.

Could you give me a hint who to renew this?

Best regards,

 on: January 11, 2018, 02:40:27 PM 
Started by KdG - Last post by Derek Read
It does appear to be functioning oddly. I'll let the development team know.

 on: January 10, 2018, 05:11:32 AM 
Started by KdG - Last post by KdG
I noticed that since XMetaL Author Essential the OpenString function hangs when you add the [boolTemplate]
So Documents.OpenString(doc,1,"test.xml",false); causes no response
While Documents.OpenString(doc,1,"test.xml"); works fine.

Is this a general thing or just someting with my installation?

Steps to reproduce: Copy-paste the example from the Programers Guide (below) into XMetaL:

// XMetaL Script Language JSCRIPT:
var xmlDec = '<?xml version="1.0"?>';
var docType = '<!DOCTYPE Article SYSTEM "journalist.dtd">';
var contents1 = "<Article><Title>New Document</Title>";
var contents2 = "<Para>Contents</Para></Article>";
var doc = xmlDec + docType + contents1 + contents2;
// Open the document in Tags On view

 on: January 05, 2018, 12:08:57 PM 
Started by luskds - Last post by luskds
We are having some problems with XMetal not opening documents due to a "Server Busy" error.  We get this with Windows 10 users running XMetal 10 and 12.  Users are running Windows 10 version 1511, 1607, and 1607 with the current updates.  XMetal is both Essentials (concurrent license) and Enterprise.  We have some success with the two following workarounds, but the problems don't go away.  If a workaround works (they don't in all cases), it has to be repeated every time XMetal is opened.  Workarounds:
1.  Hold down the Ctrl key when you open a doccument and skip the last session's workspace.
2.  Clear all files in C:\Users\<your_id>\AppData\Local\Temp before opening XMetal

Any ideas?

 on: December 27, 2017, 07:56:41 AM 
Started by MarcB - Last post by MarcB
Using XMetaL Author Enterprise on Windows 7 with default DITA version set to 1.2 in the DITA Options.

We are noticing the following behavior when including references to DITA maps from within a DITA map in conjunction with the @navtitle attribute. If the referenced DITA map is a regular map, XMetaL shows the value of the @navtitle attribute as before. If the referenced DITA map is a bookmap, the @navtitle attribute is ignored and the ID value of the referenced map is displayed.

Reference to a regular map:
<topicref format="ditamap" scope="local" href="command_central/_command_central_help.ditamap" navtitle="Command Central Help"/>

Reference to a bookmap:
<topicref navtitle="Element ID :bookmap_A5B7B17D145749FC9C631614A439B8AC" href="installer/_using_installer.ditamap" scope="local" format="ditamap">

This happens with <topicref> and <mapref> alike, starting with XMetaL 12.

I understand the @navtitle is deprecated with DITA 1.2, but we have many DITA maps with that attribute, including nested DITA bookmaps, and they are now all displaying the Element ID as navtitle.
A workaround is to set the @locktitle attribute to "yes" on the topicref, but my question is: what should we be doing? What is the recommended format of a topic reference in a DITA map?

Marc Beckers
Software AG

Pages: 1 2 3 4 5 6 7 8 9 10
email us