2015-12-04 17:42 GMT+01:00 Henrik Nergaard <henrin10@student.uia.no>:

Case 17178 added an extra check to the handling of mouse movement to use the result from asking the event handler by default (if the morph has an event handler) in the same way as other ���handles��� methods behaves. The default behaviour for Morph event handling is that if an event handler is present for a morphic object it is up to its class to specify which events that uses the event handling mechanism or not.

��

GLMSystemWindow>>#initialize creates an event handler for itself, which then causes the #handlesMouseMove: to return false since it has an event handler, but it does not handle #mouseMove.

��

One solution could be to remove GLMSystemWindow>>#initialize and implement #keyStroke: instead.

��

>>keyStroke:

��

super keyStroke.

self handleKeyStroke: evt.

��

Other possible solution could be to implement #handlesMouseMove: in GMLSystemWindow with the logic necessary.

��

Another possibility is to only return early in Morph>>#handlesMouseMove: Iff the event handler has an event registration for #mouseMove.

��

I would go with the first solution, and remove the need for an event handler object in GLMSystemWindow.


I would go with the third solution, return early only if handlesMouseMove returns true.
(The handles mouse move seems somewhere special, maybe because all Morphs supports to be dragged and move, and therefore some Morphs may not care
to install a mouse move eventhandler.)
��

��

��

Best regards,

Henrik

��

��

From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Andrei Chis
Sent: Friday, December 4, 2015 4:31 PM
To: Pharo Development List <pharo-dev@lists.pharo.org>
Cc: Moose-related development <moose-dev@list.inf.unibe.ch>
Subject: Re: [Pharo-dev] GTDebugger not draggable with latest VM

��

Seems to happen due to the fix in��issue 17178

��

On Fri, Dec 4, 2015 at 4:21 PM, Andrei Chis <chisvasileandrei@gmail.com> wrote:

Seems that starting with Pharo 50483 one cannot drag the inspector/playground/debugger.

��

No idea what happened.

��

On Fri, Dec 4, 2015 at 3:19 PM, Blondeau Vincent <vincent.blondeau@worldline.com> wrote:

Hi,

��

I have a problem on the latest Moose6.0 image.

I was not able to open a Roassal view, I had a NativeBoost Generic failure���

So I updated the VM to last stable, and, now, the GTdebugger and the Moose panel are not draggable anymore���

Can somebody is able to reproduce the problem?

��

Thanks

��

Cheers,

Vincent

��


Ce message et les pi��ces jointes sont confidentiels et r��serv��s �� l'usage exclusif de ses destinataires. Il peut ��galement ��tre prot��g�� par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm��diatement l'exp��diteur et de le d��truire. L'int��grit�� du message ne pouvant ��tre assur��e sur Internet, la responsabilit�� de Worldline ne pourra ��tre recherch��e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp��diteur ne donne aucune garantie �� cet ��gard et sa responsabilit�� ne saurait ��tre recherch��e pour tout dommage r��sultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

��

��