Hi Bernhard,

I wanted to mention that until Aaron's most recent release, most new apps were 
created with the WE Script Framework app, which also created the basic xml file 
(which included the menu for the app).  This is always one other option should 
you run into any other issues with UIDesign (I have to admit, I never even knew 
UIDesign could not create an app menu because I always created my apps this 
way).

Also, I am still amazed by all the things UIDesign can do; if there was ever an 
app I would hate to try to write myself, it probably would be UiDesign.  I 
guess this is a way of saying that writing a mostly general purpose xml editor 
(which is at the same time a specialized xml editor for WE) is just amazing.

Even when I am one of those pointing out problems, I just wanted to mention 
what a great app it is, and what a prime example of what can be done with 
Window-Eyes apps.

Chip





Chip Orange
Florida Public Service Commission
Computer Systems Analyst
850-413-6314


-----Original Message-----
From: Scripting 
[mailto:scripting-bounces+corange=psc.state.fl...@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/corange%40psc.state.fl.us.
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