[Cuis-dev] Flickering with some widgets
Juan Vuletich
juan at cuis.st
Thu Jul 16 08:23:43 PDT 2026
Hi Folks,
Just pushed a few updates addressing the issues you both raised.
#handlesKeyboardFocus is now false by default, and usually there's no
need for a different implementation, or for a #handlesKeyboardFocus
property.
Please test. Hope this helps.
Thanks,
On 2026-07-16 6:08 AM, Hilaire Fernandes via Cuis-dev wrote:
>
> Do you consider a Morph to be, by default, a widget or a shape?
>
> Another point, it should be implemented as a morph property, as it is
> done for other testing event methods.
>
> Consider my initial example with PluggableListOfMorph, the contents of
> the list are bordered box morph. I don't want to subclass it to set
> handlesKeyboardFocus to respond to my need, true or false.
>
> So an additional suggestion is
>
> Morph>>handlesKeyboardFocus
>
> ^ self hasProperty: #'handlesKeyboardFocus'
>
> Also, please add some comments to the method. What does it mean it
> handles keyboard focus? Is it to respond to TAB keyboard or something
> else? It is not clear to me.
>
> Thanks
>
> Hilaire
>
> Le 16/07/2026 à 07:44, Luciano Notarfrancesco via Cuis-dev a écrit :
>> I was thinking, perhaps Morph>>handlesKeyboardFocus should answer
>> false so that morphs don't get focus by default unless you implement
>> this method? Would that lead to more predictable behaviour? What's
>> the advantage of the current behaviour? It just saves you from
>> implementing handlesKeyboardFocus in your morphs or does it have any
>> other advantage?
> --
> http://mamot.fr/@drgeo
>
--
Juan Vuletich
www.cuis.st
github.com/jvuletich
researchgate.net/profile/Juan-Vuletich
independent.academia.edu/JuanVuletich
patents.justia.com/inventor/juan-manuel-vuletich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20260716/59e4fbbe/attachment.htm>
More information about the Cuis-dev
mailing list