Pages: « 1 2 3 4 5 6 7 8 9 10 »
 21 
 on: March 04, 2019, 05:52:21 PM 
Started by dmurphy - Last post by Derek Read
This doesn't sound like a standard feature of XMetaL Author Enterprise to me.

Please check with the vendor for the CMS you are working with to see if this is a window they have added to XMetaL Author's UI, why it might be appearing in this instance, and if they know about the issue and whether they have a fix for it.

If you are sure this is something that is part of XMetaL Author's UI (perhaps I misunderstand from your description) having a screenshot of it might help clarify.

 22 
 on: March 04, 2019, 03:57:18 PM 
Started by MichaelLohr - Last post by XMetaLOldTimer
A similar issue was reported by another customer last September and repaired in late October last year.   Redownload the v12.0 which contains XMAX binary v12.0.0.081 and the problem should be fixed there.

Here is the summary of the related issues fix in the latest XMAX 12.0 software:

ArchitectureCannot open document if its corresponding DTD or XSD was located in a deeply nested folder structure. The per-user generated folder path XMAX made for writing compiled rules file was longer than Windows would permit.
ArchitectureCannot open document if its corresponding DTD or XSD was located in a deeply nested folder structure AND APPDATA is set to a UNC-based folder path. The per-user generated folder path XMAX made for writing compiled rules file was longer than Windows would permit.


 23 
 on: March 04, 2019, 12:57:44 PM 
Started by dmurphy - Last post by dmurphy
I am using XMetaL 12. A window with a gray background keeps popping up and overlaying the topic I have checked out. It occurs when I have entered something in Attribute Inspector, and pressed Tab, but it doesn't appear every time I enter something and press Tab. The window has "Active Tool Windows" and "Active Files" headers on it, listing the windows and files I have open. With that window open, I can't select or do anything. Pressing Esc causes it to go away. What is this window for, and how can I prevent it from appearing?

 24 
 on: February 20, 2019, 07:48:40 PM 
Started by akheiljain - Last post by akheiljain
We are in the process of migrating to Oxygen Author and will like to migrate the user word lists created by users over the years, in order to do that we need to access the UWL files. I have a tried multiple applications with no luck to open these files. The workaround which is very time consuming would be to open the spell checker in XMetal and copy each ignored word to a text editor one by one. Please suggest a better way of doing this.
Thanks in advance.

 25 
 on: February 14, 2019, 02:20:01 PM 
Started by MichaelLohr - Last post by Derek Read
If you have time to test XMAX 13 now is a good time to provide feedback on it that might make it into version 14.

 26 
 on: February 14, 2019, 02:19:06 PM 
Started by MichaelLohr - Last post by Derek Read
We have been releasing major versions annually for quite a while, but specific dates for XMAX are hard to nail down. "Summer" is a good guess.

XMetaL Author Enterprise typically comes out in March (this is the biggest selling product and is always released first) followed by XMetaL Author Essential (essentially the same product minus a bunch of features), then XMAX. All of those products have a large shared codebase.

XMetaL Developer (if we do one that year) and the CMS integrations that we maintain ourselves usually follow in the fall (XMetaL Author Enterprise for SharePoint and Documentum).

 27 
 on: February 07, 2019, 06:34:32 AM 
Started by MichaelLohr - Last post by MichaelLohr
Thanks for your help.

I tested it again with XMAX 13 and now I got the same message box as you. And after that XMAX is working.
With XMAX 12 this message box was not shown, so there must be some kind of improvement.

So I will check on our side if it is possible to upgrade to XMAX 13.

Do you know when XMAX 14 will be ready because updating all our customers is not that easy and if we could
change to the newest version this would be very helpfully?

Best regards,
Michael





 28 
 on: February 06, 2019, 05:54:49 PM 
Started by MichaelLohr - Last post by Derek Read
I have repeated the same test but this time without mapping the drive letter and instead using a network path similar to yours:

\\servername\data\home\dread\roaming

No problems in this case either.

 29 
 on: February 06, 2019, 05:44:49 PM 
Started by MichaelLohr - Last post by Derek Read
This is what I see when testing with XMAX 13 and your solution, after having moved my %appdata% folder to a Windows share that is mapped to the O: drive (something I already have in place), and making sure there is no SoftQuad folder there (which there isn't by default of course since the "roaming" folder was just created by me and is new). After XMAX created it the first time I removed it again and XMAX had no trouble creating it again, nor writing into it.

In this dialog XMAX is telling us that it is writing out it's minimum set of customization files. I'm not sure if that is normal for your setup. I assume there is no document-level customization simply because this is a stress test. If for whatever reason you cannot work around this problem perhaps providing a full set of customization files will avoid XMAX having to write here (since it can simply load them all from the DTD location).

Here are some guesses:

1. Somehow (without knowing about this issue, nor knowing how to reproduce it) we have altered the way XMAX 13 accesses %appdata% and reads/writes to it. I think that is unlikely as we are using standard Windows APIs for this. It is possible that the Microsoft compiler or code that we used for XMAX 12 is different for 13 (some update has been applied or similar) though I don't think that is the case.

2. Somehow the folder you have pointed %appdata% to on your test system is not functioning the way Windows needs it to, or at least those APIs that we use to read/write files.

3. Something else is interfering with all of this, perhaps some additional 3rd party code is required to reproduce the issue that I do not have. This might be part of your own code, or perhaps it is something entirely separate, such an an anti-virus or other kind of security software, or perhaps the server where these files are stored is somehow behaving oddly when it comes to Windows client machine access.

 30 
 on: February 06, 2019, 02:15:46 PM 
Started by MichaelLohr - Last post by Derek Read
I will have a look.

I am testing with XMAX 13 so that might be the difference. You should also try the current release of XMAX on your side to see if that helps. There isn't much point in testing with 12. If there is an issue with that version a fix for it won't be created. If the issue is reproducible in version 13 then (given current development workflow) it would likely be addressed in version 14.

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