Pages: « 1 2 3 4 5 6 7 8 9 10
 91 
 on: February 04, 2019, 04:19:24 PM 
Started by MichaelLohr - Last post by Derek Read
Each user needs to have their own separate %appdata% location for XMAX (which I think would typically be created for each user/account on a Terminal Server session, or maybe I don't understand how you can configure such a system). If a folder is being shared among users then temp files written there by each copy of XMAX might trigger a race condition and that is not something the software is designed to handle.

If that doesn't sound like the issue you are seeing we will need more information about the setup.
If a Terminal Server is involved and you are not using concurrent licensing then perhaps that is part of the issue?

 92 
 on: February 04, 2019, 04:07:53 PM 
Started by pmasal - Last post by Derek Read
This user will need to run the full (EXE) installer package again as the temp files that it unpacks (the MSI and other files) have been deleted from the system after the last time they ran it.

The EXE we provide is a self-extracting archive that unpacks a large number of files to a temp folder (by default the folder you have shown in the screen capture), effectively unpacking what used to be shipped out to users as a CDROM (and something you can still burn onto a CD if you want to back it up and share that around, though not many people have CD drives any longer). Once it has been unpacked the actual installer runs. If those files are deleted then a repair is not possible without re-running the full (EXE) installer package.

 93 
 on: February 04, 2019, 02:53:49 PM 
Started by pmasal - Last post by pmasal
--------------------
Derek's solution (described in his response to my original post) worked perfectly.
Modifying this post because I'm having trouble with the Reply function (site indicates that too many replies have been tried).
Paul M.
--------------------

One of our users is experiencing variable results from the Insert menu within XMetaL Enterprise 12.0.0.081 with the SDL Tridion Docs authoring bridge (sometimes the Insert menu displays only a few options, sometimes the entire range of options). Since no other users seem to be having the issue, I asked her to first Repair her install, but we're seeing the messages shown in the attached screen shots (I suggested a reboot and then re-run repair - the same thing happened).

The strange thing is that we used an EXE file to install XMetaL 12 and an associated patch (we don't have the requested MSI file). I also checked all local permissions for AppData, the XMetaL Program Files folder, and the associated authoring bridge folders - all are accessible and write-able. Any ideas about what I can do next? Thanks!
Paul M.
McAfee

 94 
 on: February 04, 2019, 07:08:40 AM 
Started by MichaelLohr - Last post by MichaelLohr
Hi Derek,

we are using XMAX12 in a C# application.

One of our customers have a terminal server where the %appdata% folder for every user is mapped to a network share.
On this system it is not possible to initialize the XMAX control.

Do you know this problem and do you have a solution for this?

Best regards,
Michael



 95 
 on: January 31, 2019, 05:03:54 AM 
Started by PhilB - Last post by TimothyAveri
Hi everyone
Sorry, if this question have already an answer, but i wasnt able to found one...

Is there a way to have, lets say :
- Green Brightness at value 64 for Off Color
- Green Brightness at value 127 for On Color ?

Thanks in advance for your help

 96 
 on: January 30, 2019, 06:26:32 PM 
Started by A S - Last post by Derek Read
I recall this bug. It was introduced sometime between version 8 (?) and 10 and was corrected sometime between version 10 and 13, though I'm not sure exactly when. I think it was introduced with version 8 because of a conflict with the new feature added that slides windows out of the way ("pin" and "auto hide").

I've tested the behaviour in 13 (current release) and see the expected behaviour.

A value entered in the Attribute Inspector should be set when you perform the following actions:
- move to a different attribute (in the Attribute Inspector) for the same element using the mouse or tab key
- press enter
- put focus back into the same document using the mouse
- put focus into a different document using the mouse

Pressing the Esc key will return to the document without setting the attribute.

Note that this applies to setting values directly in the Attribute Inspector only. If an attribute is set in a form (even one launched from the Attribute Inspector) the logic for how attributes are set is contained entirely within the form and may vary depending on the customization and how the form was designed to function.

 97 
 on: January 30, 2019, 06:05:21 PM 
Started by A S - Last post by A S
In XMetaL 10 Author, when a user is working on a topic in Tags On view and they enter an attribute value using the Attribute Inspector, the value is not saved unless the user clicks in a different attribute field before leaving the Attribute Inspector. If a user enters an attribute value in the Attribute Inspector and then clicks in the main window, the att inspector closes without saving the new att value. As a result, users assume the attribute value has been saved, when it has actually been deleted. Requiring users to click in a different, blank attribute field in order to save an entered attribute value is inconvenient.

Steps to reproduce:
1. Open a topic in XMetaL 10, in Tags On view.
2. Add a new tag pair and click after the opening tag.
3. Open the Attribute Inspector.
4. Type a value in one of the attribute fields and click in the topic pane.
The Attribute Inspector closes.
5. Open the Attribute Inspector and verify that the value entered in step 4 is not present.
6. Type a value in one of the attribute fields and click in a different, blank attribute field.
7. Click in the topic pane.
The Attribute inspector closes.
8.  Open the Attribute Inspector and verify that the value entered in step 6 is present.

 98 
 on: January 09, 2019, 06:13:32 PM 
Started by rshubert - Last post by Derek Read
The feature does not exist in version 12, it was added in 13, so...

Unless there is some technical reason (reliance on 3rd party integrations is really the only one) for not upgrading that's still your best option I think. Clients with "maintenance" (which is every customer we have aside from very specific exceptions) can upgrade for "free" (that's actually what you pay maintenance for), if cost is the concern.

Another technical reason for not upgrading of course would be that your company has tested version 12 and is happy that it is stable with everything else you are doing (not necessarily 3rd party software but processes, configuration settings, etc) and that upgrading might be considered a risk.

If this feature is important I would recommend testing it in the trial version to see if it meets your needs, then perhaps check to see if you can (ie: your organization "allows" it) to upgrade to 13.

Antenna House is a partner* and what they are showing on that page (the one you have referenced) seems to be the existing functionality for working with subject schemes in the Japanese edition of XMetaL Author Enterprise 12. If anything, support in 12 (Japanese edition and the regular edition that you have) would be limited to (I believe) editing files that use the subjectScheme.dtd. XMetaL Author can handle any DTD, so that would have been possible as soon as that DTD existed, though having XML template as a starting point makes it easier too so maybe we included templates in 12. It doesn't have any of the actual support for subject schemes, ie: using the content of a subjectScheme saved in one file to work with attribute values in a topic or map (which is the feature added to 13).



* We provide support for Antenna House Formatter as part of our integration with the DITA Open Toolkit to produce PDF using that engine -- the "deliverables" for that in our UI are listed as "PDF via Antenna House Formatter and PDF5-ML plugin" and "Antenna House VIA PDF2" (and possibly other names in releases older than 13).

 99 
 on: January 09, 2019, 11:47:49 AM 
Started by rshubert - Last post by rshubert
Hello,

We recently upgraded to XMetaL 12 so I won't have the option to upgrade to XMetaL 13.
We are using a DITA Subject Scheme. I did happen to find an example online that looks like it's using XMetaL 12 to apply a DITA Subject Scheme to attributes, sadly the instructions are in Japanese. https://www.antenna.co.jp/xmetal/new-feature12.html#pagelink11. See second animated graphic on this page.

Is there no functionality in XMetaL 12 outside of the customization to do this?

Thanks,
Ryan

 100 
 on: January 08, 2019, 03:04:43 PM 
Started by rshubert - Last post by Derek Read
That forum example should work in versions up to 13 (and continue to work thereafter). In general, customizations for older versions will continue to work for newer ones (provided APIs are used in the way they were designed). However, for DITA, and because you are asking specifically about subject schemes, I don't think that's the best option. For non-DITA DTDs I would still recommend that demo as a starting point (but see "Non-DITA" below). The DITA authoring customization also does not generally support this level of modification (as it is easy to break existing features when adding script).

DITA Subject Schemes:
Your best option might be to upgrade to XMetaL Author Enterprise version 13. In version 13 we added support for working with DITA subject schemes. You can create them (as a DITA document), manage them, and attach them to maps and topics. Once you have attached one to a document the values for that scheme are listed in the Attribute Inspector for the particular attributes defined in the subject scheme. The resulting UI is the same as you see for an attribute with enumerated values (ie: when the DTD defines an enumerated list of values for the attribute and not simply CDATA). If you download the trial version from the xmetal.com website you will get the current release (which is as of this posting version 13). Two new items appear on the Reuse menu ("Apply/Remove Subject Scheme" and "Show subjectScheme Manager") and the documentation discusses the feature as well. If you try this feature, I would recommend using the example subjectScheme listed in the DITA documentation for the <subjectScheme> topic to start with (this is accessible via our F1 help, just search for "subjectScheme").

For Non-DITA:
If that post's example looks like it would help then base whatever you want to create on it. The form will need modification to match the attribute and it's values, and you might want to trigger the form another way, perhaps by letting the user double click on the element, select it from a toolbar/menu, open it with a shortcut key, etc.

Another option (assuming you have control of / permission to modify the DTD or W3C Schema) is to modify the attribute to be an enumerated list. In this case the Attribute Inspector will list only those values allowed by the DTD or W3C Schema. Of course, this pretty much rules out DITA specialization as it suggests basing new attributes on @props and @base, which are themselves CDATA.

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