Re: Best practice for dummy empty option in a WOPopupButton
Re: Best practice for dummy empty option in a WOPopupButton
- Subject: Re: Best practice for dummy empty option in a WOPopupButton
- From: George Domurot <email@hidden>
- Date: Wed, 27 Feb 2008 07:03:23 -0800
Try binding the noSelectionString attribute to "> Select One <" and
see what happens.
-G
On Feb 27, 2008, at 6:53 AM, Archibal Singleton wrote:
Hi everybody,
I was wondering what would be the best way to solve the following
recurring problem:
You want to present a user with a list of options, using a
WOPopUpButton. Typically those options are some kind of EO.
By default, the first time the list is presented, the selected
(ideally the first item on the list) option would a *place holder*
to indicate that no actual option is selected.
Now my question is how best to implement this?
The idea is that the dummy place holder is just be an artifact of
the view.
But the WOPopUpButton iterates over a list of EOs so the dummy
option should somehow be a dummy EO in that list and be handled
correctly in various places (check for the selection, preventing
from saving the dummy EO, etc) which makes it hard to prevent it
from polluting my code beyond the view level.
So I'm curious to know how you guys deal with this "problem"?
Many thanks for any insight.
= tmk =
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden