Adding items in pull-down on Attribute Inspector

[tharpa]

We have inherited an old application that calls XMetaL.  Under certain conditions, the right-hand pane pull-down menu of  the Attribute Inspector is populated with some items.  We need to add an item to this list.  I am having a hard-time finding where the Attribute Inspector is getting its items from. 

Where would be a good place for me to start looking?

XMetalAuthorEssential 7.0

Reply

[Derek Read]

The Attribute Inspector lists attributes that are valid in the XML document for the current element. The list of attributes is based on the definitions in the DTD or W3C Schema for that XML document.

Reply

[tharpa]

Thanks, Derek.

Reply

[tharpa]

The Attribute Inspector lists attributes that are valid in the XML document for the current element. The list of attributes is based on the definitions in the DTD or W3C Schema for that XML document.

So I was able to make a small change in the DTD and get it to reflect in the Attribute Inspector.  However, I have changed it back but my change still displays in the Attribute Inspector despite having removed it from the DTD.  The change endures despite rebooting twice. 

Is it cached somewhere?

Reply

[barbwire]

The Attribute Inspector lists attributes that are valid in the XML document for the current element. The list of attributes is based on the definitions in the DTD or W3C Schema for that XML document.

So I was able to make a small change in the DTD and get it to reflect in the Attribute Inspector.  However, I have changed it back but my change still displays in the Attribute Inspector despite having removed it from the DTD.  The change endures despite rebooting twice. 

Is it cached somewhere?

I think it is because so called rlx-file, which is one of the strangest thing in the XMetal. 🙂 Look the .rlx file and delete it and that should suffice.

Reply

[Derek Read]

Changes to the DTD should be automatically reflected in the RLX* file if you make changes to the main file in the DTD. However, where a DTD consists of multiple files and you make changes to a referenced file (or if file timestamps are off for some reason) there can be cases where those changes are not picked up. In this case you have two options:

1) Locate and deleted the RLX file.
2) Generate the XMetaL customization using XMetaL Developer.

If your DTD is located in a folder that you have full write permission for the RLX file will have been generated there.
If your DTD is located in a folder that you do not have write permission for the RLX file will have been generated in XMetaL's temp folder structure:
%appdata%SoftQuadXMetaLgen.rlx

*The RLX file is a compiled version of the DTD. It was originally necessary when computers were slow and compiling the DTD might take several dozen seconds, so saving the compiled version cut loading time significantly. These days it saves a second or so at most. It represents the binary version of what XMetaL uses in memory. It is possible to distribute just a single RLX file and many clients choose to do that rather than distribute the DTD. That is actually the default action when you create a customization using XMetaL Developer. There are several reasons for this: you can distribute a single file rather than many, you don't want authors making changes to the DTD (there are no editing tools for the RLX binary format), or you want to make it difficult to recreate a DTD or use it in another piece of software. There are two other similar file types: RLD for W3C Schemas (XSD schema files) and RLS for SGML DTDs.

Reply

[tharpa]

So I was able to make a small change in the DTD and get it to reflect in the Attribute Inspector.  However, I have changed it back but my change still displays in the Attribute Inspector despite having removed it from the DTD.  The change endures despite rebooting twice. 

Is it cached somewhere?

I think it is because so called rlx-file, which is one of the strangest thing in the XMetal. 🙂 Look the .rlx file and delete it and that should suffice.

Thank you.  This did the trick.  I tried to reply earlier, but the forum software seems to be buggy.  It often tells me I can't reply because I must wait 180 seconds, so the post is suspected to be spam, when in reality I've waited a day.

Reply

[Author]

Posts