Thanks Johan, now I'm in the right path. I have implemented basic
persistence and now I'm working on the add/remove promote/demote node
operations and I need to revisit the body persistence after that to make
it work on each node.
Cheers,
Offray
On 26/07/16 15:32, Johan Fabry wrote:
No,
No, this is not in initializePresenter, since this is called only once, when
the window is opened. Instead, you need to do this every time that the widget
is changed. So in your code where you change the widget to a new one, I guess
this is changeBody: , you need to configure this new widget.
Thanks Johan for your quick answer.
Your hypothesis is right and the contents of (4) are cleaned by a new
widget when I click at the tree (2). I'm looking at my code and
documentation, but I can't find properly how to implement your
recommendation. I imagine is somewhere in
I think the problem is that when you click on an item in the tree (2), the
contents of (4) is changed to a new widget. As a result the configuration that
you did in initializePresenter is lost. What you should do is when you change
the contents of (4) also configure this new widget with a
Hi,
I'm migrating my grafoscopio interface from I'm trying to capture some
changes in a text morph that is part of a Spec interface. The interface
is split in 4 parts, as you can see at [a]: (1) a main menu, (2) a tree,
(3) a node header input text and (4) a text morph. When you click any
