2016-02-04 8:17 GMT+01:00 stepharo <stepharo@free.fr>:

I do not like the API :)

Hi Steph, Julien,

Iooked at the fix for this issue.

Implementing #activate on WindowModel and delegate to

self window

of course works.

But I am unsure if we want to do it that way, because messages like

#maximize #minimize are implemented differently.

I don't know what is the�� preferred way for models to communicate with widgets through the adapter. But if we

follow�� the way of maximize and minimize, an implementation for

WindowModel>>#activate

could be

�� self changed: #activate with: #()

and this needs another change in MorphicWindowAdapter>>#activate

�� self widgetDo: [ :w | w activate ]

what do you think?

��

Le 3/2/16 13:35, Julien Delplanque a ��crit :

Ok I found how to do it:

myWidget window window activate.

Some observations:
"myWidget window" gives a WindowModel which inherits from AbstractWidgetModel and does not have #activate message.
"myWidget window window" gives a SpecWindow which inherits from StandardWindow, a morph.

Thanks a lot for the help!

Julien

On 03/02/16 13:16, Sven Van Caekenberghe wrote:

<window-model> window activate ?

On 03 Feb 2016, at 13:03, Julien Delplanque <julien@tamere.eu> wrote:

On 03/02/16 12:33, Stephan Eggermont wrote:

On 03-02-16 12:14, Julien Delplanque wrote:

Hello,

I can't find the answer by browsing classes comments nor methods so I
ask the question here :).

Is it possible to put a WindowModel on top of all other windows opened?
If it is, how?

I'm not sure where you are looking for, but did you look at the WorldModel?

Stephan

How, a little precision, when I say "Is it possible to put a WindowModel on top of all other windows opened?" I mean programatically of course :p.

Julien