Smalltalk › Pharo › Pharo Smalltalk Users

Halo Menu On Spec Tree Node

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

Adventurer

Halo Menu On Spec Tree Node

Hi All,

I had an issue - when I opened a Halo on a Spec tree node in the UI and select the menu Icon, I got a DNU message. However if I selected a normal Morph, the menu Icon worked fine.

I'm using Pharo 4.0 released version.

Fixed this by changing TreeModel>>iconFor to:
iconFor: aNode
^ iconBlock value cull: aNode contents cull: aNode

Craig

Nicolai Hess

Re: Halo Menu On Spec Tree Node

2015-05-06 13:47 GMT+02:00 Craig Johnson <[hidden email]>:

Hi All,

I had an issue - when I opened a Halo on a Spec tree node in the UI and select the menu Icon, I got a DNU message. However if I selected a normal Morph, the menu Icon worked fine.

I'm using Pharo 4.0 released version.

Fixed this by changing TreeModel>>iconFor to:
iconFor: aNode
^ iconBlock value cull: aNode contents cull: aNode

Hi,

Thank you for the report (and the fix)

I made a bugtracker entry:

15500

SpecTreeNodeModel(Object)>>doesNotUnderstand: #content

Craig

Sergio Fedi

Re: Halo Menu On Spec Tree Node

Thanks for making the new case, I may resolve it soon.

Nicolai Hess

Re: Halo Menu On Spec Tree Node

2015-05-06 21:23 GMT+02:00 Sergio Fedi <[hidden email]>:

Thanks for making the new case, I may resolve it soon.

Good luck :)

I put a slice into the inbox, but that fix does not work , fo example:

RemotesManager new openWithSpec.

does not work anymore

stepharo

Re: Halo Menu On Spec Tree Node

In reply to this post by Nicolai Hess

Thank you both...
I'm getting burned from this Mooc. Reviewing slides all day long with Damien and Luc.

Le 6/5/15 20:27, Nicolai Hess a écrit :

2015-05-06 13:47 GMT+02:00 Craig Johnson <[hidden email]>:

Hi All,

I had an issue - when I opened a Halo on a Spec tree node in the UI and select the menu Icon, I got a DNU message. However if I selected a normal Morph, the menu Icon worked fine.

I'm using Pharo 4.0 released version.

Fixed this by changing TreeModel>>iconFor to:
iconFor: aNode
^ iconBlock value cull: aNode contents cull: aNode

Hi,

Thank you for the report (and the fix)

I made a bugtracker entry:

15500

SpecTreeNodeModel(Object)>>doesNotUnderstand: #content

Craig