Le 19 mai 2015 à 18:04, webwarrior a écrit :
I want to make a tree using TreeModel that reacts to changes in underlying
data - when an item changes, tree node for that item should update its state
(recompute its children, etc.).
Rebuilding the whole tree is ok, as long as selections and
Actually, I may be using slightly newer version of Spec straight from github
repository
--
View this message in context:
http://forum.world.st/Spec-TreeModel-dynamic-contents-tp4827440p4827820.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
version 30854
On 21.05.2015 14:16, Nicolai Hess [via Smalltalk] wrote:
2015-05-21 13:05 GMT+02:00 webwarrior [hidden email]
/user/SendEmail.jtp?type=nodenode=4827816i=0:
Using lots of trial and error, I finally found a solution. Or,
rather a hack.
In Pharo 3:
Just set
2015-05-21 13:05 GMT+02:00 webwarrior r...@webwarrior.ws:
Using lots of trial and error, I finally found a solution. Or, rather a
hack.
In Pharo 3:
Just set autoRefreshOnExpand to true, and then when there is need for
update, do:
I can not find autoRefreshOnExpand anywhere in Pharo3.0.
Using lots of trial and error, I finally found a solution. Or, rather a hack.
In Pharo 3:
Just set autoRefreshOnExpand to true, and then when there is need for
update, do:
self widget treeModel updateList
In Pharo 4:
For some reason autoRefreshOnExpand was removed, and now we also have to
Hi,
I believe that you need to work a bit more at the Morphic level;
MorphTreeMorph and MorphTreeNodeMorph have everything you need. The
problem seems to be in the way Spec provides an API for those features
(or does not provide an API).
Regards,
Thierry
Le 20/05/2015 20:28, Nicolai Hess
2015-05-19 18:04 GMT+02:00 webwarrior r...@webwarrior.ws:
I want to make a tree using TreeModel that reacts to changes in underlying
data - when an item changes, tree node for that item should update its
state
(recompute its children, etc.).
Rebuilding the whole tree is ok, as long as
I want to make a tree using TreeModel that reacts to changes in underlying
data - when an item changes, tree node for that item should update its state
(recompute its children, etc.).
Rebuilding the whole tree is ok, as long as selections and
collapsed/expanded state of nodes are preserved.
