> FT is FastTable. This is a project begun by Esteban to replace the old
slow list on Pharo.
> Pharo 5 uses FastTable now.

Thanks for the details. Should I update to Pharo5 tu use FT ?

As for my progress in debugging things. I see that the roots and the children behave differently (although they are created equal by my nodeFromTreeStructure: method), for instance, root nodes are not inspectable, when I try to see them in an inspector I get : MessageNotUnderstood SpecTreeNodeModel>>gtInspectorMorphIn.

Children nodes can be seen in the inspector without a hitch.

Also, root nodes know their widget (a MorphicTreeNodeAdapter) whereas the children return nil.

Any help, even just a reference at someplace to look, would be appreciated.

On Mon, 26 Oct 2015 at 11:49 Ferlicot D. Cyril <cyril.ferlicot@gmail.com> wrote:
Le 26/10/2015 10:38, Edouard KLEIN a ��crit :
> What is FT ?
>

FT is FastTable. This is a project begun by Esteban to replace the old
slow list on Pharo.
Pharo 5 uses FastTable now.

> I did some debugging. When I send the selected:#true message to a root
> node, it goes down to the Morphic classes, and everything is fine, when
> I send it to a child node, the dependents array of the TreeNodeModel is
> nil, so nobody gets the message. I don't know enough about Spec yet to
> understand what dependents are and why there are none on a child node.
>
> Because I really need to get this done quickly, I will try to write a
> quick and dirty fix in a subclass that will directly talk to the morphic
> objects underneath.
>
> Now, with some guidance from you guys, I would be really happy to take
> some time and write some useful code that could solve this problem
> correctly, and have it commited for anyone to use. But first, in order
> to justify to my employer that coding with Pharo was a good choice, I
> need to make my application work.
>
> I'll update here as I go.
>
>

--

Cyril Ferlicot

http://www.synectique.eu

165 Avenue Bretagne
Lille 59000 France