[NEURE-73] Check boxes and iterations Created: 02/Mar/2009 Updated: 02/Jan/2014 Resolved: 02/Mar/2009 |
|
| Status: | Closed |
| Project: | NEURE |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.6.7 |
| Type: | Task | Priority: | Critical |
| Reporter: | Pekka Räsänen | Assignee: | Oleksandr Maslov |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
All |
||
| Description |
|
When you have check boxes in a card with iterations, it seems that when you run the task and you select check box, that selection is inherited to the next card, if the next card is the next iteration. |
| Comments |
| Comment by Oleksandr Maslov [ 03/Mar/2009 ] |
|
Yes you are correct. Here is the explanation why and workaround (taken from java-doc of ButtonGroup): "Initially, all buttons in the group are unselected. Once any button is selected, one button is always selected in the group. There is no way to turn a button programmatically to "off", in order to clear the button group. To give the appearance of "none selected", add an invisible radio button to the group and then programmatically select that button to turn off all the displayed radio buttons. For example, a normal button with the label "none" could be wired to select the invisible radio button." |
| Comment by Pekka Räsänen [ 02/Mar/2009 ] |
|
Defining explicitly selected to false did not change the inheritance behaviour. |
| Comment by Oleksandr Maslov [ 02/Mar/2009 ] |
|
this is basic behavior for the object's properties: In case of checkboxes, 'selected' has default value false. That is why first time (in 1st iteration) it appears unselected, but on the next iteration it will not reset its value to default, so it will be selected or unselected (depends on the actions) Just explicitly set 'selected' to false for the 1st iteration and it will be working like you wish. |