Pages: « 1 2 3 4 5 6 7 8 9 10 »
 21 
 on: September 28, 2018, 03:13:16 PM 
Started by JRP - Last post by JRP
I'm using XMetal 11 Author Enterprise version 11.0.0.066.

Is it possible to use WScript.CreateObject in a macro to enable event handling from .NET objects?  When I try to use the following jscript in a macro, the code fails to create the object.

   var objTest = null;
   objTest = WScript.CreateObject("testEvents.testEvent","objTest");


As I understand it, creating objects using new ActiveXObject or CreateObject generically does not allow the script to consume events raised from an object.  Any help with processing events raised from .NET objects would be appreciated.

 22 
 on: September 28, 2018, 04:03:50 AM 
Started by MichaelLohr - Last post by MichaelLohr
I've tried it with XMAX13 but the behaviour is the same and the application crashes also.
Attached you find two videos.
In the first one the background spell checking is deactivated and everything works fine. In the second one it ist activated and the application crashes on the first try.

Do you have any other ideas?

Best regards,
Michael

 23 
 on: September 28, 2018, 03:54:56 AM 
Started by MichaelLohr - Last post by MichaelLohr
I've tried it with XMAX13 but the behaviour is the same and the application crashes also.
Attached you find two videos.
In the first one the background spell checking is deactivated and everything works fine. In the second one it ist activated and the application crashes on the first try.

Do you have any other ideas?

Best regards,
Michael

 24 
 on: September 27, 2018, 02:53:46 PM 
Started by MichaelLohr - Last post by Derek Read
I would recommend upgrading to the current release (13) and trying to reproduce the issue there.

 25 
 on: September 27, 2018, 05:36:18 AM 
Started by MichaelLohr - Last post by MichaelLohr
Dear Derek,

We are using XMAX 12 integrated in a C# application.

After updating from XMAX10 to XMAX12 we got some hard to find application crashes.

E.g. the application crashes if we call "Selection.Surround(name.LocalName);" on a element with a lots of content
but only if "BackgroundSpellchecking" is set to true and if we do the surround action a multiple time in a short time.

It seems that the spell checking tries to access the internal XMAX document which is in an invalid state?

Do you have any experiences with this kind of errors or has anything changed in the process of background spellchecking
from XMAX10 to XMAX12.

Best regards,
Michael

 

 26 
 on: September 24, 2018, 12:07:43 PM 
Started by pmasal - Last post by pmasal
We recently upgraded to XMetaL 12 with SDL Tridion Docs 2018. Since the upgrade, we are seeing a few strange behaviors:
  * All objects that we check out from the CMS and edit with XMetaL 12 assign a "cid" attribute to every DITA element.
  * When editing DITA topics that have conref'd elements within table cells, some of the conrefs can be selected/highlighted, but others can't (the selection appears to happen, but the highlighting does not, so the user doesn't know the conref'd element is actually selected).

Has anyone seen these behaviors before? Many thanks for any help you can give. I plan to cross-post this to the SDL technical community.

Paul Masalsky
McAfee

 27 
 on: September 17, 2018, 09:31:38 AM 
Started by adamm - Last post by adamm
I am using XMetaL(R) Author Enterprise 13.0.

I want to implement context-sensitive webhelp in our product. Is there a plugin available for the DITA OT that will generate a context id help map created from a resourcid in the prolog? Does anybody have an example of how they integrated this with XMetal? I don't see a lot of information in the forums for context-sensitivity or anything recent.

Thanks

 28 
 on: September 11, 2018, 09:08:28 AM 
Started by pmasal - Last post by pmasal
We were able to resolve the issue by unregistering XMetaL (using the XMetaL 8 unregister executable provided by Just Systems) and then repairing XMetaL (via Programs and Features).
Paul M.

 29 
 on: September 11, 2018, 08:20:46 AM 
Started by pmasal - Last post by pmasal
We are currently using XMetaL 8 with SDL Live Content Architect 2013 (soon to be upgraded to SDL Tridion Docs 2018). One of our users has installed XMetaL 8 but the SDL Authoring Bridge install can't find XMetaL (says that XMetaL 8 is not installed, but we can see it fine in Windows Programs and Features). Does anyone know:

 * If XMetaL 8 must be fully licensed on the machine before the Authoring Bridge install can detect it (the license server for XMetaL 8 is no longer in service because it is so down-level - Just Systems provided an "unregister" executable for us, so we can use it until the upgrade).

 * What the SDL CMS authoring bridge install checks to detect XMetaL (i.e. a specific registry key).

Many thanks for any help you can give. I have posted this to the SDL Community as well.

Paul Masalsky
McAfee

 30 
 on: September 07, 2018, 02:16:21 PM 
Started by gopinathselvamin - Last post by Derek Read
Following is from the readme file included with the installer for XMetaL Author Enterprise For Teamcenter.
Similar information should be included with the online help available after the software has been installed.

Quote
Creating New DITA Documents
Now that you have a templates folder containing template files, you can create new documents based on them.

Note: The "File" menu in XMetaL Author is used to interact with the local file system. A special "Repository" menu is used for all file-related actions when working with content management systems that integrate with XMetaL Author Enterprise, including Teamcenter.

1. In XMetaL Author Enterprise for Teamcenter, select the "New from Repository Template..." item listed in the "Repository" menu.
2. In the dialog that appears navigate to the template folder (the folder you created, or that you shared, using the previous steps in this topic).
3. Select one of the template files listed in the folder and click the "Continue" button.
4. Select a location to save your newly created document to, provide a name, then click the "Save" button.
5. A new document based on the template you selected will be created in the CMS at the location specified and the document will be checked out for editing in XMetaL Author Enterprise for Teamcenter.* At this point you may add additional content to complete the document and check it back into the CMS using the "Check in Document" item listed in the "Repository" menu.

* At the same time as the XML file is checked out and copied to your computer, the associated DTD or W3C Schema and other files needed to provide the authoring experience (these include CSS, CTM, and possibly MCR and other files) should be provided by the CMS in the same location (via the CMS connector) so that XMetaL Author has access to them. If properly configured this will occur automatically without you needing to do anything.

The above procedure will be the same for most CMS systems that integrate with XMetaL Author Enterprise and all CMS systems that integrate using "XMetaL Connector", including those provided by 3rd parties. We provide the Repository menu and associated actions and APIs to allow CMS developers to build a "connector" that will work with their specific CMS functionality while allowing us to develop and test this common interface. There are some CMS vendors that have chosen not to use these standard interfaces but we encourage them to do so as it makes things more predictable, leading to (hopefully) a more stable environment.

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