Re: [Pharo-project] Destiny of changed:/update:

using on:send: instead of changed/ is a nice way to reduce extra updates. In Cuis juan kept only one mechanism and I like that. In VisualWorks you have to use on:send:to: this way you can select with facet is refreshed. So I would like to deprecated changed. Stef

Will changed:/update: disappear and be totally replaced by Announcements?

I ask because I'm using ListModel and noticed that it sends a generic "self changed: #selectionIndex". I built a GUI that had two of them, and couldn't differentiate between the updates, so I was going to enhance it a little.

-- View this message in context: http://forum.world.st/Destiny-of-changed-update-tp4234693p4234693.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.