2014-12-28 15:59 GMT+01:00 Roberto Minelli <roberto.minelli@usi.ch>:

By "PluggableButtonMorph contained in the TakskbarMorph” I mean the PluggableButtonMorph that sits in the TakskbarMorph and “represents” a given SystemWindow in the IDE space.

Usuallay this works with dependents or announcement registrations. That means, if the SystemModel is the "model" of the PluggableButtonMorph, the PluggableButtonMorph is the SystemWindows dependents array, and/or the button registers himself for the SystemWindows announcer. But actually I am a bit suprised, because it seems the TaskbarMorph rebuilds its whole TaskbarButton array *everytime* something changes. For example, I have 4 workspaces open PluggableButtonMorph allInstances size. -> 8 Click multiple times on the 4 workspace taskbar buttons or put the different Workspace windows to front: PluggableButtonMorph allInstances size. -> 40 Smalltalk garbageCollect. PluggableButtonMorph allInstances size. -> 8

Hope it is clear.

Thanks for any help!

Cheers, R

...

On 28 Dec 2014, at 15:50, Roberto Minelli <roberto.minelli@usi.ch> wrote:

Hi,

I am trying to understand some Morphic. It looks like the dark side.

Anyway, I am trying to reconstruct the relationship between a Morph, say a SystemWindow and its PluggableButtonMorph contained in the TakskbarMorph. Any suggestion?

Each PluggableButtonMorph in the TakskbarMorph has as #model the “real” window, but I cannot find the inverse relationship.

Cheers, R