Bruce, perhaps you used an older version of the manual to work from (they do add new object model features every release so far). Also, WE Script Framework has really been improved, so that you can position a cursor on an object such as "menu" in your editor, and press it's hotkey, and it will bring up help for that object. the various peculiarities where it might not work unless it was surrounded by spaces have all been fixed, and it's a real help if you find the manual difficult to navigate, since it will take you right where you need to go; give it a try, it has options for going directly into the app reference manual, and into the object browser which the WE Script Framework provides. Chip
_____ From: BT [mailto:[email protected]] Sent: Monday, May 23, 2011 9:31 PM To: [email protected] Subject: Re: Object Manual and Poor Explanation Hi Chip, thanks, I had made a text copy of the manual and it was not there. but when going back to the one in the help menu, it was as you stated below. so, so much for making a text copy of the manual...unless I got it from an old file, but can't remember. this is the first time I used any of these features. Meaning a dialog or menu, at least in the WE model. When I first did the Cuckoo Clock I was using the existing Hourly chime format and not looking at the XML file for much but adding check boxs and radio buttons and such. So, the understanding that the menu is new, placed in a different location, is helpful, but still confusion. I will read again from the WE help manual and see if there is a better explanation. check the .chm, and see what is going on with that text version I have. So, will get back to step by step adding my Cuckoo clock methods and test them. The timeTextValues function I wrote is a nice conversion for 12 to 24 hour format...Once I made sure I did a ByVal inside it. Like I have mentioned many times, you also need a road map for the manual. Bruce Sent: Monday, May 23, 2011 9:02 PM Subject: RE: Object Manual and Poor Explanation Oh, and Bruce, below is the entry from the text property of the menu object (which is in the objects in the app developer's reference manual): Navigation: The Window-Eyes Object Model > Objects > Menu > Properties > Text Previous page Return to chapter overview Next page Sets or returns a string used for a specified menu item. Syntax Retrieving string_value = object.Text(Id) where object is a Menu object. Setting object.Text(Id) = string_value where object is a Menu object. Requirements Window-Eyes 7.1 or greater. _____ From: BT [mailto:[email protected]] Sent: Monday, May 23, 2011 8:36 PM To: [email protected] Subject: Object Manual and Poor Explanation Hi! I mentioned to Chip today that the setting up menu's along with the IniFile default, in both cases there lacking in good explanations and details. The IniFile default is only good as an alternative to having nothing and not for setting a default...only good for testing. Below is what I figured out but not from a direct reading of the Object manual. first in the manual you get an explanation of the menu and it's setting up along with a simple example. then down in the dialog section it mentions in an example how to get a menu item, but it is not the same. Nothing mentioned to why that example and the other menu object and it's example are different, but works in the event. then, with no explanation nor examples, nor any properties the creation of a menu object is given in the dialog section... BANG! so, why was one mentioned way back, then mentioned with parens later, but no connection between the 2 and the need for one gets the other? The parens shown are not even needed but placed in the example. Once I figured out that you had to create the menu in the dialog then the other syntax came into play, but no clue until I figured it out. Anyway, below works, and you have to create the menu inside the dialog even though when monitoring the events you use dialog format, but not until you create the menu object, then and only then can you use the menu properties... NOTE: I had to guess that Text would be a property for there was no mention of that any where in the manual... Very frustrating, if giving classes, can't you at least get the manual a little better reading? Working Dialog with menu's: Set myDialog = dObj Set myDialogMenu = dObj.Menu myDialogMenu.Checked( "menu_hourly_DateTime") = INIFile(myINIFile).Number( "Configuration", "Enhance_Hotkey", False) myDialogMenu.Text( "menu_edit_sleep") = timeTextValues( "Sleep Edit: ", sleepHour, sleepMinute) myDialogMenu.Text( "menu_edit_wakeup") = timeTextValues( "Wakeup Edit: ", wakeHour, wakeMinute) myDialogMenu.Text( "menu_edit_alarm") = timeTextValues( "Alarm Edit: ", alarmHour, alarmMinute) Bruce
