Hi Chip and Aaron,
I did not test to see if it is just a long, because the example for a
simple dialog states objects and as Chip points out below, data can be a
string. The simple dialog also states even objects.
I think the long value is for index items and not the actual data. But,
testing it to see what happens is the best way, but data being text makes
perfect sense. Just item fetching does need to be a pointer, or long number
as you state. I think the confusion is only over which property or method we
are talking about.
Sincerely
Bruce
----- Original Message -----
From: "Chip Orange" <[email protected]>
To: <[email protected]>
Sent: Wednesday, November 30, 2011 8:12 PM
Subject: RE: SimpleDialogs Update
Hi Aaron,
Please see the below; it's copied from the app developer's ref manual, and
is why I thought "variant" meant it was ok to store additional data which
was an object in the listbox item?
Do I need to change my examples file, or is this documentation actually
correct?
Chip
----------
Navigation:
The Window-Eyes Object Model
>
Objects
>
Control
>
Control Types
>
ListBox
>
Methods
>
Add
Previous page
Return to chapter overview
Next page
Returns the index of an item added to a list box. Items are added to the end
of an
existing item list.
Syntax
long_value = object.Add(Text, Data)
where object is a
ListBox
object.
Parameters
Name
Data Type
Required/Optional
Description
Text
String
Required
String of the item to be added
Data
Variant
Optional
Data (or value) of the item to be added
-----Original Message-----
From: Chip Orange [mailto:[email protected]]
Sent: Wednesday, November 30, 2011 8:09 PM
To: [email protected]
Subject: RE: SimpleDialogs Update
Thanks for the update Aaron, that was quick.
Sorry David; looks like it was my bad about storing additional data with
each listbox item (I see I say this in class#30, so I'll get the examples
file updated).
Chip
-----Original Message-----
From: Aaron Smith [mailto:[email protected]]
Sent: Wednesday, November 30, 2011 3:29 PM
To: [email protected]
Subject: Re: SimpleDialogs Update
Bruce,
Correct. You can't store objects themselves in the listbox data property.
The documentation indicates that a listbox data property is a long value. So
you'd have to store some sort of index instead, and then correlate that to a
file object.
Aaron
On 11/30/2011 3:16 PM, BT wrote:
> Hi Aaron,
>
> Yes, that I thought would be a simple fix since the standard
> dialog
has the FocusedItem property and a simple move over to the simple one with
just using a different name for it, for easy reading could be done.
>
> Now about the set issue error. You did a simple text assignment,
> but
in the notes for a simple dialog when an object is being used in an
assignment, it states that it requires the assignment to be using the Set
Command.
> So, when looking at Daves issue, he is using a file object, so I
suggested that he look at that and the error of not set would in fact come
up.
>
> So, try duplicating the error using file objects as Dave did. I
> have
not since I had meetings today and just got home. but I think that is what
is going on with Dave's issue.
>
> Sincerely
> Bruce
>
> ----- Original Message -----
> From: "Aaron Smith"<[email protected]> To:<[email protected]>
> Sent: Wednesday, November 30, 2011 1:28 PM
> Subject: SimpleDialogs Update
>
>
> Greetings,
>
> The latest version of the GW Toolki (8.4.4) has support for the
> DefaultSelect property in the SimpleDialogs object:
>
> Set s =
> SharedObjects("com.gwmicro.gwtoolkit.simpledialogs").listboxdialog
> s.additem "red", "red"
> s.additem "green", "green"
> s.additem "blue", "blue"
> s.sort = true
> s.defaultbutton = "&Select"
> s.cancelbutton = "Close"
> s.DefaultSelect = 2
> print s.ChooseItem("Select a color")
>
> That would result in a dialog with the green list box item
> automatically selected.
>
> Aaron
>
--
Aaron Smith
Web Development * App Development * Product Support Specialist GW Micro,
Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.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 GW Micro Technical
Support Team.
