our app in a couple places does stuff where a user clicks on a button
whose action in turn employs openDropDownListWithEvent: on a combo box to force the list to drop down, if the user actually makes a selection everything is fine. However, if the user does not and just clicks on an empty piece of real estate what then occurs is that the action button in question i.e. that which called #openDropDownListWithEvent on the combo box does not get its exit event i.e. not quite then. A second event is required i.e. for example just clicking once again on empty real estate or any other widget for that matter will then force the event to be dispatched to the button. So in the exception scenario i.e. when the user does not make a selection from the drop down list there is a failure to process the exit event , so it gets deferred and processed later at the wrong time. In VW 3.0 all of this works fine but it does not in 7.x , well at least not in our app ported to 7.x. My guess is that this is a MPUI related issue and perhaps I'm not familiar enough with the api provided. Not sure if its fair to classify this as a bug but I do think that it is reasonable to expect developers to be able to programatically drop down a combo box list to the same effect as if a user had done so and to be able to do so without much setup i.e. I think it would be nice to call one specific method. I'm attaching a simple test UI with steps labelled on the UI that recreate the problem. I have also attached a pic of the UI in case folks are scared of loading the .st file :) thanks in advance, -- Charles A. Monteiro http://wiki.nycsmalltalk.org http://www.monteirosfusion.com http://monteirofusion.blogspot.com |
what ? no bites :)
On Mon, 31 Jul 2006 12:54:25 -0400, Charles A. Monteiro <[hidden email]> wrote: > our app in a couple places does stuff where a user clicks on a button > whose action in turn employs > openDropDownListWithEvent: on a combo box to force the list to drop down, > if the user actually makes a selection everything is fine. However, if > the > user does not and just clicks on an empty piece of real estate what then > occurs is that the action button in question i.e. that which called > #openDropDownListWithEvent on the combo box does not get its exit event > i.e. not quite then. A second event is required i.e. for example just > clicking once again on empty real estate or any other widget for that > matter will then force the event to be dispatched to the button. > > So in the exception scenario i.e. when the user does not make a selection > from the drop down list there is a failure to process the exit event , > so > it gets deferred and processed later at the wrong time. > > > In VW 3.0 all of this works fine but it does not in 7.x , well at least > not in our app ported to 7.x. > > My guess is that this is a MPUI related issue and perhaps I'm not > familiar > enough with the api provided. > > Not sure if its fair to classify this as a bug but I do think that it is > reasonable to expect developers to be able to programatically drop down a > combo box list to the same effect as if a user had done so and to be able > to do so without much setup i.e. I think it would be nice to call one > specific method. > > I'm attaching a simple test UI with steps labelled on the UI that > recreate > the problem. > I have also attached a pic of the UI in case folks are scared of loading > the .st file :) > > thanks in advance, > > -- Charles A. Monteiro http://wiki.nycsmalltalk.org http://www.monteirosfusion.com http://monteirofusion.blogspot.com |
Free forum by Nabble | Edit this page |