This is most likely true but I want to make sure everyone is clear that
you really don't need the toolkit for this. Yes, it makes it easier but
it certainly isn't required. Meaning you can create your own dialog
with the list box and do it all yourself. There are many examples
(including the toolkit itself) that show how this is done.
Doug
On 10/20/2010 9:13 PM, Chip Orange wrote:
I agree with you Jeff, I'm seeing the same issue. I don't think it's
anything we can solve, I think this will have to be fixed in the next
release of the toolkit.
Chip
------------------------------------------------------------------------
*From:* Jeff Weiss [mailto:[email protected]]
*Sent:* Wednesday, October 20, 2010 3:12 PM
*To:* [email protected]
*Subject:* using the shared object listbox
I want to use the shared object simpleDialogs.ListBox to have an
option to either copy the entire list to the clipboard or close
without copying.
The way the listbox seems to work is that if you select an item, that
item text is returned when the default button is pressed. Nothing is
returned when the cancel button is pressed.
The closest thing I can figure is to use the cancel button to copy
text to the clipboard because it always returns a 0 length string.
Here is the problem---if the OK button is selected without selecting
anything in the listbox, a 0 length string is also returned.
Is there another way to determine which button was pressed?
Or better yet, is there a way to make sure the first item is always
selected---as in:
focusedIndex = 1
Aaron and others, I would appreciate your suggestions.
Thanks,
Jeff Weiss
