On 28/09/15 18:59, Federico.Balaguer wrote:

Hello,

I found a problem with BotArena (http://smalltalkhub.com/#!/~FedericoBalaguer/BotArena) on Pharo 4.

BotArena is an interactive robot simulation environment that we use in my university to teach OOP basics. BotArena was developed as an instantiation of BOSS (http://smalltalkhub.com/#!/~CAR/BOSS/).

BotArena (as well as BOSS) has a window (Morph) that has three buttons and a grid view that is subclass of BorderedMorph. The GridView can handle RedButtons, a click on the grid adds a new robot to the simulation.

The problem that raised on Pharo4 is that, after a RedButton event, any event (focus to another pharo window or clicking on one of the buttons of BotArena) will be handled by the GridView.

It seems like the GridView retains the focus after the (first) RedButton event was handled.

Could someone help me to sort this one out?

What is the entry point to the application? I could start a BGSCar2012DemoSimulation, and that doesn't allow extra robots. Stephan

2015-09-28 18:59 GMT+02:00 Federico.Balaguer <federico.balaguer@gmail.com>:

Hello,

I found a problem with BotArena (http://smalltalkhub.com/#!/~FedericoBalaguer/BotArena) on Pharo 4.

BotArena is an interactive robot simulation environment that we use in my university to teach OOP basics. BotArena was developed as an instantiation of BOSS (http://smalltalkhub.com/#!/~CAR/BOSS/).

BotArena (as well as BOSS) has a window (Morph) that has three buttons and a grid view that is subclass of BorderedMorph. The GridView can handle RedButtons, a click on the grid adds a new robot to the simulation.

The problem that raised on Pharo4 is that, after a RedButton event, any event (focus to another pharo window or clicking on one of the buttons of BotArena) will be handled by the GridView.

It seems like the GridView retains the focus after the (first) RedButton event was handled.

Could someone help me to sort this one out?

Quick solution: use self on: #click send: #mouseDownEvt: to: self. in BotArenaGridView for registering the event dispatcher. The problem is a change I did in 40422. I tried to fix another issue with for the #click action. Now we have to find a solution that works for both, #mouseDown and #click. nicolai

Thanks! Federico

-- View this message in context: http://forum.world.st/Morph-event-handler-on-wrong-morph-submorph-tp4852370.... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Hi federico could you - show it to damien when he will come to Laplata? - could you produce a small video because I would like to share it with other teachers? Stef Le 28/9/15 18:59, Federico.Balaguer a écrit :

Hello,

I found a problem with BotArena (http://smalltalkhub.com/#!/~FedericoBalaguer/BotArena) on Pharo 4.

BotArena is an interactive robot simulation environment that we use in my university to teach OOP basics. BotArena was developed as an instantiation of BOSS (http://smalltalkhub.com/#!/~CAR/BOSS/).

BotArena (as well as BOSS) has a window (Morph) that has three buttons and a grid view that is subclass of BorderedMorph. The GridView can handle RedButtons, a click on the grid adds a new robot to the simulation.

The problem that raised on Pharo4 is that, after a RedButton event, any event (focus to another pharo window or clicking on one of the buttons of BotArena) will be handled by the GridView.

It seems like the GridView retains the focus after the (first) RedButton event was handled.

Could someone help me to sort this one out?

Thanks! Federico

-- View this message in context: http://forum.world.st/Morph-event-handler-on-wrong-morph-submorph-tp4852370.... Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.