[ 
https://issues.apache.org/jira/browse/PIVOT-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280800#comment-16280800
 ] 

Roger Whitcomb commented on PIVOT-971:
--------------------------------------

Add test/demo features to the CheckedListViewTest program.  Also added an 
Adapter class to ListViewItemStateListener for completeness (since the 
interface now has two methods).
Sending        tests\src\org\apache\pivot\tests\CheckedListViewTest.java
Adding         tests\src\org\apache\pivot\tests\checked_list_view_test.bxml
Sending        wtk\src\org\apache\pivot\wtk\ListViewItemStateListener.java
Transmitting file data ...done
Committing transaction...
Committed revision 1817316.

> Add the ability to have tri-state checkboxes in ListView
> --------------------------------------------------------
>
>                 Key: PIVOT-971
>                 URL: https://issues.apache.org/jira/browse/PIVOT-971
>             Project: Pivot
>          Issue Type: New Feature
>          Components: wtk, wtk-terra
>    Affects Versions: 2.0.4
>         Environment: All
>            Reporter: Roger Whitcomb
>            Assignee: Roger Whitcomb
>            Priority: Minor
>              Labels: listview
>             Fix For: 2.1
>
>         Attachments: listview.diffs, tri-state listview.png
>
>
> For one place in our application, a ListView is used along with checkboxes, 
> but it seems like it would be good to be able to use tri-state checkboxes 
> here, such that a mixed state could be indicated for some entries.  But, then 
> the question becomes:  if the checkbox is mixed, is it checked or not?  Two 
> thoughts on that:
> 1. Add a method to get the checkbox state for all items, so you can check 
> yourself if they are checked, unchecked or mixed.
> 2. Add a property "mixedAreChecked", which if set true (default false) would 
> make the mixed state entries show up as checked.
> Also, how do you set the "mixed" state for an item?  Not sure about that yet.
> Altogether:  lots of implications throughout the code to support this feature.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to