Comments on: Two ways to programmatically work with a combobox, and still use the change event handler http://johnwilker.com/2007/10/Two-ways-to-programmatically-work-with-a-combobox-and-still-use-the-change-event-handler/ John Wilker: Community, Code, Randomness Tue, 24 Jan 2012 20:39:04 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Rich http://johnwilker.com/2007/10/Two-ways-to-programmatically-work-with-a-combobox-and-still-use-the-change-event-handler/comment-page-1/#comment-3365 Rich Tue, 15 Jun 2010 23:15:26 +0000 http://www.johnwilker.com/j/index.cfm/2007/6/29/Two-ways-to-programmatically-work-with-a-combobox-and-still-use-the-change-event-handler#comment-3365 FOr what it's worth, I get unreadable blue text on grey background FOr what it's worth, I get unreadable blue text on grey background

]]> By: Cyril http://johnwilker.com/2007/10/Two-ways-to-programmatically-work-with-a-combobox-and-still-use-the-change-event-handler/comment-page-1/#comment-3079 Cyril Wed, 27 Jan 2010 09:40:57 +0000 http://www.johnwilker.com/j/index.cfm/2007/6/29/Two-ways-to-programmatically-work-with-a-combobox-and-still-use-the-change-event-handler#comment-3079 Creating and firing change events might trigger something else elsewhere, and from documentation change event fire on USER interaction. So I prefer Tom's solution. Except that having a method that receive an event.. or not.. is, as you said, less clear, and might be source of error. Apply a bit of refactoring: first you should name your handlers "handleXxx" or "onXxx" private function onNewSavedScheduleSelection(e:ListEvent):void { var listFiringTheEvent:ListBase = ListBase(e.target); selectNewSavedSchedule( listFiringTheEvent.selectedItem); } private function selectNewSavedSchedule( selectedSchedule:SavedScheduleVO):void { your actual code... } onShow() can now set selectedItem and call selectNewSavedSchedule. Creating and firing change events might trigger something else elsewhere, and from documentation change event fire on USER interaction. So I prefer Tom's solution. Except that having a method that receive an event.. or not.. is, as you said, less clear, and might be source of error.

Apply a bit of refactoring:
first you should name your handlers "handleXxx" or "onXxx"
private function onNewSavedScheduleSelection(e:ListEvent):void
{
var listFiringTheEvent:ListBase = ListBase(e.target);
selectNewSavedSchedule( listFiringTheEvent.selectedItem);
}

private function selectNewSavedSchedule( selectedSchedule:SavedScheduleVO):void
{
your actual code…
}

onShow() can now set selectedItem and call selectNewSavedSchedule.

]]> By: jwilker http://johnwilker.com/2007/10/Two-ways-to-programmatically-work-with-a-combobox-and-still-use-the-change-event-handler/comment-page-1/#comment-2992 jwilker Thu, 31 Dec 2009 17:03:02 +0000 http://www.johnwilker.com/j/index.cfm/2007/6/29/Two-ways-to-programmatically-work-with-a-combobox-and-still-use-the-change-event-handler#comment-2992 Sounds like a personal problem. Cut-n-paste into the editor of your choice I guess. Sounds like a personal problem. Cut-n-paste into the editor of your choice I guess.

]]> By: Zanpher http://johnwilker.com/2007/10/Two-ways-to-programmatically-work-with-a-combobox-and-still-use-the-change-event-handler/comment-page-1/#comment-2991 Zanpher Thu, 31 Dec 2009 16:50:24 +0000 http://www.johnwilker.com/j/index.cfm/2007/6/29/Two-ways-to-programmatically-work-with-a-combobox-and-still-use-the-change-event-handler#comment-2991 Sorry, can't read code that isn't colored correctly. (normal colors, black on white bg). Sorry, can’t read code that isn’t colored correctly. (normal colors, black on white bg).

]]> By: Tom Ortega http://johnwilker.com/2007/10/Two-ways-to-programmatically-work-with-a-combobox-and-still-use-the-change-event-handler/comment-page-1/#comment-1281 Tom Ortega Wed, 07 Jan 2009 02:45:07 +0000 http://www.johnwilker.com/j/index.cfm/2007/6/29/Two-ways-to-programmatically-work-with-a-combobox-and-still-use-the-change-event-handler#comment-1281 Ahh..but you see. The only reason I suggested it was because you "weren't" looking at the event. :) Obviously if your working with the event, that would be very dangerous and not a nice way to go. If you want to plan for the future, then I'd say create a separate function from the handler. One that excutes when that value changes, than call that function from the show and handler function. This way, your event logic never mixes with the change logic. Ahh..but you see. The only reason I suggested it was because you "weren't" looking at the event. :)

Obviously if your working with the event, that would be very dangerous and not a nice way to go.

If you want to plan for the future, then I'd say create a separate function from the handler. One that excutes when that value changes, than call that function from the show and handler function. This way, your event logic never mixes with the change logic.

]]> By: Tom Ortega http://johnwilker.com/2007/10/Two-ways-to-programmatically-work-with-a-combobox-and-still-use-the-change-event-handler/comment-page-1/#comment-233 Tom Ortega Fri, 12 Oct 2007 00:00:00 +0000 http://www.johnwilker.com/j/index.cfm/2007/6/29/Two-ways-to-programmatically-work-with-a-combobox-and-still-use-the-change-event-handler#comment-233 Ahh..but you see. The only reason I suggested it was because you "weren't" looking at the event. :) Obviously if your working with the event, that would be very dangerous and not a nice way to go. If you want to plan for the future, then I'd say create a separate function from the handler. One that excutes when that value changes, than call that function from the show and handler function. This way, your event logic never mixes with the change logic. Ahh..but you see. The only reason I suggested it was because you "weren’t" looking at the event. :)

Obviously if your working with the event, that would be very dangerous and not a nice way to go.

If you want to plan for the future, then I’d say create a separate function from the handler. One that excutes when that value changes, than call that function from the show and handler function. This way, your event logic never mixes with the change logic.

]]>