Hi Samuel,

You are right about what you said but we were doing something like this:

1. we remembered the current focus holder.
2. then we activated the MenuMorph, FIllInTheBlank and thus setting a new
focus holder.
3. and finally we restored the focus to the morph on 1.

But this wasn't right. I will give you this escenario as an example.

The focus is on a browser code pane and you right-click on a category list
morph. The menu that popups obtain focus and you select 'add category' then
new. A FillInTheBlank popups and get focus. The previous MenuMorph is
deleted. You enter the new category name and accept it. The FillInTheBlank
ends and return the focus to the .... MenuMorph which is no more on the
world.

The right solution I would think would be to implement a more complex
structure than what we were doing, but sincerely I am not qualified to do
it. I am very much afraid of the inners of Morphic :)

So. The above solution (or no solution at all) will still leave us with the
problem of typing without cursor. My proposed fix will still leave us
without cursor but at least when you start typing it will appear. But I
concede that is more of a hack than a solution and I will more than gladly
accept others ways to fix this problem.

Regards,
Hernan

> -----Original Message-----
> From: squeak-dev-bounces at lists.squeakfoundation.org
> [mailto:squeak-dev-bounces at lists.squeakfoundation.org]On Behalf Of
> Samuel Tardieu
> Sent: Monday, April 12, 2004 5:58 AM
> To: squeak-dev at lists.squeakfoundation.org
> Subject: Re: [FIX][BUG] Hidden text cursor ( v4 - a more general
> solution? )
>
>
> >>>>> "Hernan" == Hernan Tylim <htylim at yahoo.com.ar> writes:
>
> Hernan> I found that all the previous changesets wasn't really fixing
> Hernan> the cursor problem. That was because we were remembering just
> Hernan> the previous focus holder, not the whole chain (which I think
> Hernan> would add unwanted complexity).
>
> I think this is the correct thing to do.
>
> Hernan> This is what this change set will do. It will modify
> Hernan> handleKeyDown: Morph>>handleKeyUp: and Morph>>handleKeystroke
> Hernan> so they set the receiver as the keyboard focus holder when
> Hernan> they receive a keyboard events.
>
> I think this is the wrong thing to do. You will not see the cursor
> until after a character is pressed if I understand correctly.
>
>   Sam
> --
> Samuel Tardieu -- sam at rfc1149.net -- http://www.rfc1149.net/sam
>