Pages: « 1 2 3 4 5 6 7 8 9 10 »
 on: April 23, 2018, 10:13:25 AM 
Started by Marvin - Last post by Marvin
We curently use XMetal Author 9 (yes, we're working on upgrading to a newer version) and have some "XRef" elements we don't want to allow to be empty.

From what I've read, DTDs don't support that restriction (only XSD schemas do).
Also, it would be nice if users could get immediate feedback when they move the selection away from the XRef element, and not only when they save the document, which could possibly be much later.

I have tried to use the On_Update_ElementList event for this, but I can't seem to figure out where to go from there:
It seems like you can't even open message boxes, so I struggled to even see what was happening (or if my macro was called at all).

Any help would be highly appreciated.

 on: April 18, 2018, 03:23:14 PM 
Started by lchiriac - Last post by Derek Read
Here are some things to try:

1. Navigate to another website instead to see if the issue is limited to something Google is doing. Your screenshot suggests Google is serving up some code that is giving you issues.
2. Navigate to an HTML page you have stored on disk that you've created yourself. C:\temp\mytest.html or something, then put nothing into that HTML file except very basic HTML and no scripts and see if that renders.
3. Load directly into IE (and specifically not Edge which is an entirely different engine and not embedded when you use Shell.Explorer).

I'm fairly certain you would see the same IE version reported for embedded copies. If you want to try to check that you would probably need to create an HTML page that contains script that displays the value for window.navigator.userAgent, then load the page into the Resource Manager (as #2 above).

It sounds like you are dealing with this with Tom through email. I think we should try to limit the communicate for this to that one pathway.

 on: April 17, 2018, 09:58:11 PM 
Started by lchiriac - Last post by lchiriac
Hi Derek, truly sorry about that - I had a try/catch there... which I removed and I left the typo in.

Below is what I have, it does not have any syntax errors. It gives me the same error as the screenshot I attached earlier.

<?xml version="1.0"?>
<MACRO name="On_Application_Open_Complete" hide="true" lang="JScript">
   ResourceManager.Visible = true;
   ResourceManager.RemoveTab( "Assets" );
   ResourceManager.RemoveTab( "Desktop" );
   msie = ResourceManager.ControlInTab( "Demo" );
   msie.navigate( "" );


I have IE version is 11.0.9600.18952. Could that be the issue maybe... is there a way to see what version of the IE is trying to invoke when using Shell.Explorer or Shell.Explorer.2 ?

Thanks a lot for your help!

 on: April 17, 2018, 06:38:06 PM 
Started by lchiriac - Last post by Derek Read
I can't reproduce your exact issue but there is definitely a syntax error on line 6 (marked in red below):

ResourceManager.AddTab("MyTab", "Shell.Explorer.2");}

Removing the curly bracket at the end fixes that and allows the script to run properly.

 on: April 17, 2018, 04:36:16 PM 
Started by lchiriac - Last post by lchiriac
I have been trying to use the ResourceManager to add a tab and navigate to, as explained in tutorials, but I am getting errors, see attached the screenshot.

Using XMetaL Author Enterprise 10.0 or 12.0

Is it because of the .js files referenced, or am I doing something wrong?

<?xml version="1.0"?>
   <MACRO name="On_Application_Open_Complete" lang="JScript" hide="false"><![CDATA[
        // XMetaL Script Language JSCRIPT:
                ResourceManager.Visible = true;
                ResourceManager.RemoveTab( "Assets" );
                ResourceManager.RemoveTab( "Desktop" );
                ResourceManager.AddTab("MyTab", "Shell.Explorer.2");}
                var msie= ResourceManager.ControlInTab("MyTab");

Screenshot attached with the error box. Any thoughts appreciated.


 on: April 12, 2018, 06:32:52 PM 
Started by Randy316 - Last post by Derek Read
I don't think any of the APIs you might be using to move the selection have changed between these versions. APIs generally are only every modified to extend them (though this is rare). I think you've either you've found a bug or an API was being used incorrectly and happened to function the way you wanted it to in 6 but has since been fixed.

Either way, please submit a support case to XMetaL Support and include all the necessary files to reproduce the issue. XMetaL Support can have a look at it, reproduce the issue, and try to help you figure it out.

Another option would be to test again in version 12 or 13. If the issue is due to some bug with an API it may have been corrected for one of those versions (assuming a client found the same issue and reported it or it was found through testing).

 on: April 11, 2018, 10:53:25 PM 
Started by Randy316 - Last post by Randy316
I'm new to this forum so please bear with me.  I am working with XMetal Author Enterprise 11.0 on Windows 7 Enterprise version. I have a macro that searches for reference callouts and uses a popup dialog box to enter the desired ref number to search. Often we need to search for a ref number, change the text referenced by the number, then go to the next instance of the ref number and do the same thing multiple times. The macro worked fine in XMetal 6.0 but when we switched to XMetal 11.0, it stopped working in tags-on view (the dialog box pops up and allows you to enter a number, but does nothing when you click OK or press Enter); it only works now in plain-text view.  This is not useful for us as all of our input must be done in tags-on view. In order for the macro to work now, we have to switch to plain-text view, run the macro and enter a ref number into the dialog box, find the ref, switch back to tags-on view, and make any editing changes for that instance of the ref number, then repeat the whole process. Does anyone know why this macro won't work in XMetal 11.0 and/or how to make a macro that does accept input and run correctly in this version? Thanks.

 on: April 11, 2018, 01:48:15 PM 
Started by akaAnnAdams - Last post by Derek Read
The text for long results is truncated, so that code would actually need to be modified to provide more information to the results list. I believe it is truncated in order to increase the speed at which large numbers of results can be displayed. So, the amount of text here could be increased, but perhaps there are other better options...?

Double clicking on the broken link listed in the Results pane will open the DITA file that contains the broken link, and it will move the selection to the element that has that broken link (which in your case is likely an <xref>). Once you are there you can:

1) Double click on the element to open the properties dialog for it and check the full attribute value you are interested in (assuming the dialog lists it). In the case of an <xref> element for example, the dialog will display the href attribute. You can also right click and select "Properties..." from the context menu (or press the context menu key if your keyboard has one, or Shift+F10).
2) Hover over a start or end tag for the element to see the full attribute value for attributes with values that have been set.
3) Place the insertion point inside the element then open the Attribute Inspector (F6) to check all of the element's attributes.

There are some other (possibly less useful) options:
1) Switch to Plain Text view to view the <xref> element's XML source in full.
2) Copy the <xref> element and paste it into another plain text application like Notepad (which is similar to  previous option).

 on: April 11, 2018, 10:25:37 AM 
Started by akaAnnAdams - Last post by akaAnnAdams
XMetaL 12

When running the Cross-File Operation to validate references - "For each XML document, check for broken references." against all topics in a ditamap. The results identify broken links, but the actual broken link topic does not display in the results. For example:

   file not found: (fiel:///c:<folder name>/<sub-folder name>/<sub-folder name>/<sub-folder name>/<sub-fol...

our topics may have many references to the same folder, so searching for that folder doesn't help locate the broken link.

I can expand the results to show the location of the topic the broken is in, but cannot find a way to expand the column to see additional results for the actual item associated with the broken link.

Is there a way to expand the results column?

 on: April 09, 2018, 03:52:57 PM 
Started by Jaadelman - Last post by Derek Read
This sounds like an issue that affected versions up to XMAX 8 when IE9 was released (the issue was specific to changes Microsoft introduced with IE9).
That issue was resolved with the release of XMAX 9.

I cannot reproduce that same issue running XMAX 11 embedded in IE11, so presumably what you are seeing is some new issue.
I'd first double check the XMAX version. If it is lower than 9 then upgrading may correct the problem.

If the XMAX version they have is 9 or higher please submit a support case to XMetaL Support including any files needed and as much detail as necessary to make it easy to reproduce.

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