- none - is always displayed because it is the null value. Even if your relationship is mandatory, it is still displayed, because without it, the first item in the list would be automatically selected. That could lead to users saving a selection without realizing they've made it.
You can change the "- none -" string to be something less ambiguous through your rules (RHS key is 'noSelectionString') or through your localized strings (default rule uses the key 'ERD2W.noSelectionString'). If you simply disagree with the existing approach, you'll need to modify the toOne component. If you uncomment the isMandatory binding, you'll only see the null string when the relationship is optional. Although, I think the best approach would be to create a new rule key that isn't tied to the relationship and default to the existing behavior. Ramsey On Jan 12, 2012, at 9:51 AM, Theodore Petrosky wrote: > I am using the values of a popup to color rows in a table. select 'Yellow' > and the row background (css) is made yellow. > > I want to provide an attribute none (meaning no color) but the popup has an > entry for - none - (meaning none). How do I turn off the none that is > provided by d2w? > > ted > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/rgurley%40smarthealth.com > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
