Hello List,

when calling deselectAll in the qx.manager.selection.TreeSelectionManager like this:

tree.getManager().deselectAll()

calling tree.getManager().getLeadItem() and tree.getManager().getAnchorItem() still retrieve the leadItem and the anchorItem of the last selection.

Is this behaviour a bug or is this intended?

I've attached a testcase which is intended to run from frontend/demo/source/html/test.

Please select first a tree folder or a tree file.

Then click on the button "Deselect All Items" and then then button "Show Lead and Anchor Item".

You can see that the leadItem and the anchorItem is still not null as it should be.

Should I open a bug for this?


--
Mit freundlichen Grüßen
Dietrich Streifert
Visionet GmbH

Title: qooxdoo » Demo

Introducing qx.ui.tree.Tree. A first small example.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to