27 May
2010
27 May
'10
8:04 p.m.
Yes, I am interested. I never encountered this case. "tree selection"
gets the result from the #selection port.
Please describe the scenario.
Cheers,
Doru
On 27 May 2010, at 18:19, Simon Denier wrote:
On 27 mai 2010, at 13:01, Tudor Girba wrote:
--
www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot
be done."
I cannot reproduce this problem :).
Are you sure that you selected the item before hand?
Pretty sure yes, because the browser behavior relies on such a
selection otherwise.
But I can't find a simple example to reproduce the case.
If you are really motivated, I can explain how to reproduce in my
current example.
In any case, take a look at the code examples from MooseBrowsers.
For example:
MooseBrowsers>>navigationBrowserOn: scopeSelector
...
actions: [ :tree | tree selection mooseInterestingEntity
mooseFinderActions ]
Cheers,
Doru
On Thu, May 27, 2010 at 11:35 AM, Simon Denier
<Simon.Denier(a)inria.fr> wrote:
I'm trying to set some actions on items in a glamour tree
presentation, say:
actions: [:tree | tree selection xMenuItems ]
But #selection called on the widget returns nil. Is this the
expected behaviour?
I managed to get what I wanted after diving in the object:
actions: [:tree | tree selectionPath last xMenuItems ]
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev