Lost a day and got embarrassed

[bule]

I updated an app for a client and suddenly it got some weird bugs with list
duplications and similar. After a whole lost day of both me and the client
(and his temper), the issue was tracked down to a changed ComboBox behavior.

ComboBox.SetSelected() should not fire an OnSelect event.
There should be an action ComboBox.SelectItem() that would do that,
or a ComboBox.SetSelected() should have a Boolean switch for it.
The same applies to the ListBox and Tree objects.

[Derek]

ComboBox.SetSelected() should not fire an OnSelect event.

hmm ... I don't see the same behaviour!
Something else interfering with it, somehow?

[bule]

No, it was a behavior change introduced with the 1005 build of
the APMS7. When you populate the combo and then choose the
initially selected item, the OnSelect event is fired.

[Derek]

Aha! Of course. After going back to x86 from x64 couple weeks ago, i'm still using v7.1.1000.0 :rolleyes

[RizlaUK]

maybe add a optional boolean argument for all "SetSelected" actions as this causes me headaches in the listbox to, it would be nice to visualy set the selected item without setting off the actions in on select

[Imagine Programming]

maybe add a optional boolean argument for all "SetSelected" actions as this causes me headaches in the listbox to, it would be nice to visualy set the selected item without setting off the actions in on select

agreed, it's darn annoying hehe:p

[azmanar]

Hi,

I agree with Bule.

[holtgrewe]

One of the primary attributes of any new release should be 'backward compatability' - I agree 100% with bule. Setting the selection and 'firing' the On Select needs to be separate actions - if for no other reason, for compatability.

[bule]

The Slider plugin suffers from the same problem.
You set up an initial position of the slider and there it goes
firing an On PosChange event... for Heaven's sake, why?