John McNally wrote:
> If you are selecting one action from a group, I think the current scheme
> could be used without modification. If you are wanting to be able to choose
> multiple actions, modifications would be needed, but I am not sure how
> general purpose this could be made. How are you planning to order things?
>
> John
For example I have a select box with modify, delete, add and a button. When
the button is pressed it should execte eventSubmit_doDelete or doAdd depending
on what is selected.
I think the current scheme can be extended to do this, so maybe I'll work on it
this week and see what I can come up with....
> ----- Original Message -----
> From: Dan Diephouse <[EMAIL PROTECTED]>
> To: Turbine <[EMAIL PROTECTED]>
> Sent: Monday, June 05, 2000 4:19 AM
> Subject: ActionEvent and Select Boxes
>
> > I have been looking at the action event architecture and I think it may
> > be missing something. (I may be volunteering to implement it here if my
> > skills are good enough and it is not a redundant or bad idea). For each
> > button pressed on a for there is a corresponding function
> > doActionblahblah. But this only works for buttons. What if I want to
> > have a select box with a whole bunch of actions that can be chosen and
> > executed by a button? I have to do if, else if, else if or a
> > switch:.... very inconvenient :). So my questions are: Is an idea
> > worth persuing? Or is it a waste of my time? Is there a better way to
> > do it?
> >
> > Dan Diephouse
> >
> >
> >
> > ------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > Problems?: [EMAIL PROTECTED]
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
