https://bugzilla.wikimedia.org/show_bug.cgi?id=31378
--- Comment #6 from Gregor Hagedorn <[email protected]> 2011-10-05 23:55:01 UTC --- We would like to give the user an intuitive indication of the kind and form of data that can be entered into a repeatable subform. The basic problem at the moment is that the user does not see the fields she or he might be able to enter. There is no way of learning the options other than hitting a button first, which normally requires a preexisting understanding what to expect. Furthermore, in many cases, only a single record will actually be entered, and from a user perspective it is illogical that the fields to do this are not visible, whereas other fields are. (In reply to comment #5) > 1) Most importantly, in most of these cases hitting the "Add" button actually True for ASPX, but not necessarily a good design. I prefer your "add another" button (but it should be another to one existing not another of nothing). > there's only ever one blank instance form; never zero and never more than one. There were examples to the contrary. Also phpmyadmin allows more than 1 (but with a go-button each). > For the case of SF's regular forms, I just > don't know of any way for SF to know when to ignore an instance. Why does "don't save if completely empty" not work for a start? It would be ok if it does not combine with default values for the beginning. Also, I do think it is important to keep the option to start with 0 rows visible. It can stay the default if you prefer (but then perhaps change the default label of the "add another"-button...). -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
