Re^4: How to bind single click to get an path of an entry in Tk::HList

Great Ken! Exactly what i wanted. Very happy :)

Though i should be content with this, i am curious to understand how did you get this solution? selectionGet gives you the entries selected and not the paths(as per the spec). Then how did you guess that calling it within browsecommand will get the paths

Once again Thanks!!

Comment on Re^4: How to bind single click to get an path of an entry in Tk::HList

Replies are listed 'Best First'.
Re^5: How to bind single click to get an path of an entry in Tk::HList by kcott (Archbishop) on Apr 18, 2014 at 21:15 UTC
"Great Ken! Exactly what i wanted. Very happy :)" Glad I could help. "Though i should be content with this, i am curious to understand how did you get this solution? selectionGet gives you the entries selected and not the paths(as per the spec). Then how did you guess that calling it within browsecommand will get the paths" That wasn't a conscious guess on my part; however, you're quite right about the doco, so that was probably more of an implicit assumption about how that method works. `Tk` has lots of shortcuts and aliases. `selectionGet` is an alias for `infoSelection` which, in turn, is a shortcut for `info('selection')`. In the Tk::HList doco for the `info()` methods, all explicitly state that they either operate on or return entryPath(s), except "$hlist->info(selection)" — I suppose I just didn't notice the absence of "entryPath" in that particular description. Instead of "Returns a list of selected entries ..." a better description would be "Returns a list of entryPaths of selected entries ..." -- Ken	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^5: How to bind single click to get an path of an entry in Tk::HList
by kcott (Archbishop) on Apr 18, 2014 at 21:15 UTC

"Great Ken! Exactly what i wanted. Very happy :)"

Glad I could help.

"Though i should be content with this, i am curious to understand how did you get this solution? selectionGet gives you the entries selected and not the paths(as per the spec). Then how did you guess that calling it within browsecommand will get the paths"

That wasn't a conscious guess on my part; however, you're quite right about the doco, so that was probably more of an implicit assumption about how that method works.

Tk has lots of shortcuts and aliases. selectionGet is an alias for infoSelection which, in turn, is a shortcut for info('selection'). In the Tk::HList doco for the info() methods, all explicitly state that they either operate on or return entryPath(s), except "$hlist->info(selection)" — I suppose I just didn't notice the absence of "entryPath" in that particular description.

Instead of

"Returns a list of selected entries ..."

a better description would be

"Returns a list of entryPaths of selected entries ..."

-- Ken

[reply]
[d/l]
[select]