Hi, Bernhard.

UI Design requires the use of a decimal or hex language ID. So use:

language id="409" 

instead of:

language id="en-US"

The reason has to do with the fact that the language ID is used as the language 
tree node's data property, which has a data type of long. If I remember right, 
there were issues with attempting to convert language strings with locale to 
the right language id. It was never documented, because I assumed (perhaps 
incorrectly) that one would begin designing XML from UI Design rather than from 
scratch. In that case, the language ID is added in the required format from the 
beginning.

Thanks,

Aaron

-- 
Aaron Smith 
Web Development * App Development * Product Support Specialist
Ai Squared * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * www.aisquared.com

To insure that you receive proper support, please include all past 
correspondence (where applicable), and any relevant information pertinent to 
your situation when submitting a problem report to the Ai Squared Technical 
Support Team.

> -----Original Message-----
> From: Scripting [mailto:scripting-
> bounces+asmith=aisquared....@lists.window-eyes.com] On Behalf Of
> Bernhard Stöger via Scripting
> Sent: Wednesday, April 29, 2015 6:01 AM
> To: Window-Eyes Scripting List
> Subject: A well-formed XMl file that can't be displayed by UIDesign
> 
> Dear community,
> I created an XML file which does its job as the UI resource for an app, and
> which shows no error when loaded into the latest UIDesign app. However,
> when I try to explore its contents by UIDesign, I do get the tags with their
> properties, but each and every property is shown empty.
> 
> I prove this by attaching a simple test app - MenuTaurus.wepm -, which
> consists just of the named XML and a short VBS - the app does nothing but
> adding a simple menu to the WE control Panel apps menu, and, as oyu may
> see by installing the WEPM, it works.
> 
> Since I created both the XML and the VBS through some cut-and-paste from
> examples in the App Devellper's Manual, it might not be impossible that it
> may contain the one or the other uncommon character. The strange thing to
> me, however, is the fact that the Microsoft XML Parser considers it well-
> formed, whereas the uIDesign app can't display the property values.
> 
> Best wishes, from
> Bernhard
> 
> 
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: MenuTaurus.wepm
> Type: application/octet-stream
> Size: 705 bytes
> Desc: not available
> URL: <http://lists.window-eyes.com/private.cgi/scripting-window-
> eyes.com/attachments/20150429/0e28b960/attachment.obj>
> _______________________________________________
> Any views or opinions presented in this email are solely those of the author
> and do not necessarily represent those of Ai Squared.
> 
> For membership options, visit http://lists.window-
> eyes.com/options.cgi/scripting-window-
> eyes.com/asmith%40aisquared.com.
> For subscription options, visit http://lists.window-
> eyes.com/listinfo.cgi/scripting-window-eyes.com
> List archives can be found at http://lists.window-
> eyes.com/private.cgi/scripting-window-eyes.com


_______________________________________________
Any views or opinions presented in this email are solely those of the author 
and do not necessarily represent those of Ai Squared.

For membership options, visit 
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/archive%40mail-archive.com.
For subscription options, visit 
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at 
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com

Reply via email to