Comments on: ComboBox Bug

By: Bourne

Bourne — Thu, 20 Mar 2008 18:57:01 +0000

That’s not a bug. There’s an empty string in the ComboBox’s list of values, why should it treat that object any different from any of the other objects in it’s list?

It’s an easy way (or alternative way) to reset the combobox back to an unselected value if you don’t want to use the ‘prompt’ setting (as mentioned above, it has issues).

Otherwise, you’d be *forced* to use a reset button to reset the form/combobox - no, we don’t want that at all.

By: KIM

KIM — Thu, 08 Nov 2007 06:50:09 +0000

Hi Rich. here in tokyo.
great! thanks for your solution.
I’ve worried about this problem for a week!
thanks again~

By: Vent

Vent — Thu, 27 Sep 2007 04:53:07 +0000

Hi, I’m using OS 10.2 with developer tools installed from the CD in the box. I was trying to build an AS Studio application with a combo box in the interface and I came accross a strange bug. I set the combo box to generate “should begin editing” and “should end editing” events. However, whenever I would start editing the contents of the box or hit return after editing the contents, I would get an error “NSCannotCreateScriptCommandError (10)” and the event handlers wouldn’t be called. I was able to reproduce this bug reliably in the simplest manner possible. I created a new Applescript Application in Project Builder with a window in its interface and nothing in the window but a combo box set to generate “should begin editing” and “should end editing” events.

Can anybody reproduce this bug? Is it a known isssue with AS Studio? I searched all my saved emails from the AS Studio list and was unable to find any mention of this.

light bars
http://www.truckaccessorywholesale.com/specials/light_bars.html

By: Kevin again

Kevin again — Mon, 17 Sep 2007 07:53:45 +0000

And no, selectedItem and selectedValue aren’t the same thing.

By: Kevin again

Kevin again — Mon, 17 Sep 2007 07:47:57 +0000

I now believe the prompt property is pure evil and should be avoided at least in Flex 2.

We’ve found (what for us is) a showstopping bug:

Suppose I have a typical set of interlinked comboboxes for country/state/suburb.
Picking the country restricts the states which restricts the suburbs.

We don’t want a specific value to default into any of the comoboboxes, so we used the prompt value.

Country/State and Suburb are optional fields. One or more could be filled in.

The values are saved to the database. So far, so good.

HOWEVER, they can also be retrieved from the database and edited and saved again.

The damn prompt property, however, seems to override the selectedIndex and selectedItem properties……sometimes. (PS: We’re using the enhanced combobox from forta.com which has a “selectedValue” property on it. Can’t fathom how the folks at Macromedia missed that one, by the way)

This means that the comboboxes get their values blanked out by the prompt property.

I think there are issues with competing forces trying to set the selected value of the combobox and events aren’t firing in a predictable order. Is it possible that the Prompt property is sometimes evaluated after CreationComplete?

The whole interlinked comboboxes scenario is a really typical scenario for us, but we’ve had to introduce a rule “No Prompt Properties” allowed in our dev team until we can find a fix, (which may be to override the behaviour and fix the bug)

PS: We’ve also found that setting the selectedIndex to -1 doesn’t work at all when your combobox has it’s selectedValue bound to something.

Disobedient controls are really frustrating!