Den 11.07.2011 14:51, skrev Greg Brown:
The reason is that the selected path property is not defined if the TreeView is
in multi-select mode (there's no logic that defines which of the selected paths
should be considered the selected path).
IMO getSelectedPath() should return the first selected path, ie. det
first in the selectedPaths sequence. It causes no problems for me, and
I'm not suggesting to change the current behavior. I do however believe
that most people coming from other frameworks will be kind of surprised.
Easy workaround though :)
By the way, should TreeView have a getFirstSelectedNode() to be better
aligned with getSelectedPath()/getSelectedNode()? :) You already have
getFirstSelectedPath() so it kind of feels like it's missing :)
-- Edvin
