Pages: « 1 2 3 4 5 6 7 8 9 10 »
 on: May 21, 2018, 04:01:48 AM 
Started by lerche - Last post by lerche

In my XMetaL Developer project I have several JavaScript macros that are going to be bundled in an mcr-file. The default encoding format for this mcr-file is UTF-16 but I want have it in UTF-8, because my .js-Files have to be in UTF-8. Is it possible to configure the output encoding format?
Currently I have problems with letters like ä, ö, ü or ß. These letters are converted into cryptic characters.

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

Thank you for your help!

Kind regards,

 on: May 18, 2018, 02:08:02 PM 
Started by JRP - Last post by JRP
We're using XMetal on Windows 7.

We have code that runs on the FILE_CLOSE event macro that basically does some document cleanup and calls ActiveDocument.Close().  This worked fine in XMetal 7 even if the user had "tiled" their windows using the Window menu.  However, with the introduction of Tabs, and specifically Tab Groups, our macro fails to close the correct document in one specific case.  When a user has created a new "Tab Group" (horizontal or vertical), and they click the little x on the tab associated with a document that isn't the active document (their cursor is in another document), the document with the cursor closes.  In other words, clicking the x does not activate the document contained in that tab before closing.  Is this a bug?  Clicking the tab itself activates the document, but clicking the little x does not.  Any help with how we could catch this event and close the appropriate document would be appreciated.  

As an aside, if we disable our FILE_CLOSE event macro, XMetal knows to close the correct document.  We just need to know too :)

As another aside, we submitted a support case for this as well.

 on: May 16, 2018, 07:11:53 PM 
Started by davesw - Last post by davesw
Oh yeah! I should be able to use CSS to insert a text string... I'll try that route.


 on: May 16, 2018, 06:58:17 PM 
Started by davesw - Last post by davesw
Sadly it is not the nested_xft_fix INI setting. That string value is not in my local XMetaL folder and I added it to my xmetal.ini with a value of false and it had no affect.

I completely understand that more than a few embedded XFT forms would cause the app to run slower, but it is odd that this worked really quickly in XMetaL8 but does not in XMetaL11.

Before I share out a sample, is it possible to change the replacement process to insert a text string instead of an image/form? This one XML file has ~50 images and I imagine that XMetaL support will tell us that this scenario should never have worked as well as it did back in XM8...

 on: May 16, 2018, 02:59:23 PM 
Started by davesw - Last post by Derek Read
There is a chance that the INI setting nested_xft_fix is set to true. That will slow things down significantly in versions 5 and up (the functionality did not exist prior). That feature enables an element to contain an embedded XFT form and one or more children to also contain an embedded XFT form. With this setting enabled all forms are assumed to affect each other, so that every form in the document must be updated after every other form is updated, slowing things down. When that INI setting is not enabled after an XFT form is updated all of its children are assumed to not have any XFT forms.

See the third message in this thread for some additional details:,3348.msg8649.html#msg8649

If that isn't the issue then it would be best to submit a sample to XMetaL Support so they can have a look (preferably something minimal that reproduces just the one issue but contains enough to demonstrate the issue).

Keep in mind that the software has never supported running more than a few embedded XFT forms quickly as it was not designed to do so. So, the issue could simply be that having lots of XFT forms in a document makes it slow whenever it needs to be redrawn (open, switching views, or making significant changes to content).

 on: May 15, 2018, 09:52:12 AM 
Started by davesw - Last post by davesw
We recently moved from XMetaL Author Essential 8 to XMetaL Author Essential 11 (x86) and most everything worked great. One item that we are noticing is that the XFTReplacement script takes several times longer to process than it used to. We have 4 of them and they replace images and videos in our files with visual placeholders. In XMetaL8, a long XML file with 50 images would open and be ready for editing in under 10 seconds. In XMetaL11, that same file takes over one minute to load. If I turn off the 4 XFTReplacement rules that we have, that same file loads in 3-5 seconds. Is this a known issue in XMetaL11? Any workarounds to improve the performance?

Here is one of the XFTReplacement scripts (the other 3 just change the SelectorName and FormFileName):
        <SelectorName ns="">image</SelectorName>


 on: May 11, 2018, 12:50:16 PM 
Started by Randy316 - Last post by Derek Read
I would not upload anything a company owns here, especially if you need to get permission to do so. The entire world can see what is up here, which is a benefit as sometimes other users can help (that is the main purpose of the forum), but of course that also means people have access to anything you upload here.

I would recommend submitting files and any other information to XMetaL Support so it can be dealt with properly as a support case.

 on: May 11, 2018, 09:04:03 AM 
Started by Randy316 - Last post by Randy316
Thanks for your reply, Derek. I will have to discuss this with my support person at work to get permission to upload anything; I don't think we have access to any later versions of XMetal.

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: May 10, 2018, 03:01:19 PM 
Started by Marvin - Last post by Marvin
I completely agree.
I'm not sure how these invalid documents were created - normally it shouldn't be possible to create them in the first place.

But we probably have some invalid documents already at this point, so it would be great to be able to detect this.
Would be difficult to implement such validation in XMetaL, in addition to trying to avoid new document from becoming corrupted?

 on: May 10, 2018, 02:55:05 PM 
Started by Marvin - Last post by Marvin
Makes sense. Thank you!

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