Hi. I think I understand your confusion. The focus to what Romain was
referring to was the keyboard-focus. The focus that I think you are
referring to is the mouse focus.

The problem that Romain found (I'm sure he will correct me if I am wrong)
was that he would like to do something like this:

aPluggableTextMorph on: #keyDown send: #myKeyDown: to: someOtherObject.

But this don't work because a PluggableTextMorph don't have keyboard-focus.
The morph who have it is the TextMorph inside the PluggableTextMorph. So
what Romain proposes is to forward the calls #on:send:to: to the textmorph
submorph.

I can't say that I like his fix because it forward *every* #on:send:to call
to the textmorph, not only keyboard-related ones. Note that this would
prevent the setting of mouse related event handlers on the PTM.

Regards,
Hernán

> -----Original Message-----
> From: squeak-dev-bounces at lists.squeakfoundation.org
> [mailto:squeak-dev-bounces at lists.squeakfoundation.org]On Behalf Of
> frank at crystal-objects.com
> Sent: Thursday, March 25, 2004 3:15 PM
> To: squeak-dev at lists.squeakfoundation.org
> Subject: [FIX] PluggableTextMorphEventHandlerFix-rr ( [er] Is there
> enoughinformstion?? )
>
>
>
> This was in response to a bug report by the same author. The original
> bug report and this fix didn't get linked  in BFAV.
>
> There is no code to reproduce the bug or any instructions for produciing
> the bug.
>
> >From the bug report:
> "The reason is that the PTM has an embedded TextMorph, so when you click
> on
> it the (non pluggable) TextMorph gets the focus, so event handlers
> passed to the PTM are bypassed."
>
> When I bring up an inspector on a PluggableTextMorph and move the mouse
> into it the PTM gets the focus. If I then click in the PTM and type or
> edit in the embedded TextMorph the PTM still has the focus.
>
> Perhaps I'm totally missing something but I can't really tell what
> problems the author encountered.