Hi,
try it like this:
1. Collapse the tree (=close all tree nodes with the button in the
left bottom corner)
2. enter value inti iq-filter
3. select operator (=, !=, , etc.)
In tree view the filter applies only to the root elements.
If you want to filter all items switch to table view.
Hope
I've been following this patch because the app I'm working on will
really benefit from it.
Ideally, I do not want children to fall off the list to the next
page. My table will start with all children collapsed. When the user
opens a node, I would like for new rows to show up on the table. My
Setting the page size dynamically might be the best solution for my
situation.
I have lots of top-level nodes (thousands) and some of them... maybe
5% will have 2-8 children nodes. Nodes are never more than 1 child
deep. I need paging, but don't want to adjust what page an item is on
due to
Yep, this seems to be a good idea! I'll add this as an option to the
tree.
As I still would like to keep the number of items per page limited I'd
propse to present the child when expanded like this (pagesize=5):
- Numbers - Integers ...
- ...more (click to collapse)
- 56
- 57
- 58
Hi Daniel
I was testing the filters but, IQ Don't works, I put it on the field, the
117 number and nothing happened, all fields are blanking.
how works?
Please, sorry if don't work like that, and let me know the way.
Thanks.
On Tue, Nov 25, 2008 at 8:33 AM, dflorey [EMAIL PROTECTED] wrote:
BTW: Right now the filters are only applied to the top level elements.
I've tried other approaches but with confusing results for the user.
Any suggestions how to apply the filters to children are welcome!
I had the idea to add a chainsaw icon to the TreeController that will
flatten the tree to a
