From: Ramsey G. <ra...@by...> - 2010-07-01 02:15:41
|
Perhaps it would be best to leave the binding available via the context but default to false in the rules. That way, it could have a restricted choice list, a default choice pre-selected, and no way to set the value to null since having the "- please choose -" or whatever may indicate that null is an acceptable option. I agree with Anjo that this is probably a bad idea and will lead to users blindly saving values. Defaulting to the first item in the list is certainly not appropriate. Users should be required to think about their selections before saving them. Hence, the default should be false... But there is another camp of people who believe that the application should "just know" what you're supposed to pick, select it for you, and give you a filtered list of choices for cases when the default is not the appropriate choice. This can certainly cut down on repetitive menu selections on large forms. Ramsey On Jun 26, 2010, at 4:17 PM, Anjo Krank wrote: > The problem is when you have the binding true, you *don't* get the "- please choose -". So you always get the first item selected. Which IMO is a very bad idea, as the thing is normally mandatory in the sense that the user *needs* to chose sth. > > Cheers, Anjo > > > > Am 26.06.2010 um 21:56 schrieb Mark Wardle: > >> Ahah! >> >> r3923 | anjo | 2006-03-17 10:20:25 +0000 (Fri, 17 Mar 2006) | 2 lines >> >> removed the isMandatory binding. NOTE: this leads to the ' - please >> choose - ' entry always being displayed now, as opposed to simply >> seleting the first entry. IMO this is the correct behaviour, as you >> need to *choose* and entry as opposed to getting the first one and >> accidentally saving it. >> >> >> I don't think that's always the case, but subclassing this is so easy..... Or you could just work with a local copy of Wonder in your workspace and make changes whenever necessary. Even easier than subclassing when you only want to make minor modifications. Ramsey >> >> >> On 26 June 2010 20:47, Mark Wardle <ma...@wa...> wrote: >>> Hi all, >>> >>> With some reticence (I appear to be spamming the list at the moment...).... >>> >>> Is there any good reason why ERD2WEditToOneRelationship doesn't pass >>> through the d2wcontext's isMandatory key to ERXToOneRelationship? >>> >>> Surely it should include >>> >>> isMandatory = d2wcontext.isMandatory >>> >>> b/w >>> >>> Mark >>> >>> -- >>> Dr. Mark Wardle >>> Specialist registrar, Neurology >>> Cardiff, UK >>> >> >> >> >> -- >> Dr. Mark Wardle >> Specialist registrar, Neurology >> Cardiff, UK >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >> _______________________________________________ >> Wonder-disc mailing list >> Won...@li... >> https://lists.sourceforge.net/lists/listinfo/wonder-disc > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Wonder-disc mailing list > Won...@li... > https://lists.sourceforge.net/lists/listinfo/wonder-disc |