[FIX][BUG] Hidden text cursor ( v4 - a more general solution? )

Hernan Tylim htylim at yahoo.com.ar
Mon Apr 12 14:02:45 UTC 2004


Hi,
	I don't know. I think that I would prefer in that case give the focus
allways to the world than a random morph. Or, to the morph which is in that
moment under the hand and if that morph doesn't #handlesKeyboard: then to
the world. What do you think?

	And a question. Do you propose to modify each invidual case (MenuMorph,
FillInTheBlankMorph, ...) or a more general solution at the level of Morph ?

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 10:46 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> The focus is on a browser code pane and you right-click on a
> Hernan> category list morph. The menu that popups obtain focus and you
> Hernan> select 'add category' then new. A FillInTheBlank popups and
> Hernan> get focus. The previous MenuMorph is deleted. You enter the
> Hernan> new category name and accept it. The FillInTheBlank ends and
> Hernan> return the focus to the .... MenuMorph which is no more on the
> Hernan> world.
>
> Why not simply give the focus to whatever entry will get keyboard
> input if a key gets pressed? It seems to me that it would require no
> new data structure at all.
>
>   Sam
> --
> Samuel Tardieu -- sam at rfc1149.net -- http://www.rfc1149.net/sam
>




More information about the Squeak-dev mailing list