Hi Trygve.

> Isn't the changed/update mechanism between a StringMorph and filter better known and simpler?

Yes, if the list would signal "self changed: #filterTerm", the model could pass then on to the search field via a custom #update:. But usually the pluggable widgets in Squeak call models directly while models use #changed: to talk to widgets.

Anyway, another goal is to "turn off" that filter reset in the list morph after X milliseconds. It is not just the synchronization between list and field.

Best,
Marcel
Am 12.06.2020 08:57:02 schrieb Trygve Reenskaug <trygver at ifi.uio.no>:
Isn't the changed/update mechanism between a StringMorph and filter better known and simpler?
Best ... Trygve


On 2020.06.12 08:39, K K Subbu wrote:

On 11/06/20 12:02 pm, Marcel Taeumel wrote:

Yes, it was the simplest way to implement key-press response with sync between textfield and list-filter state. It occasionally bugs me too. See ListChooser >> #filterEvent:for: and the end of #buildWith:.

Marcel,

In filterEvent:for:, I see the up/down arrows being passed to listmorph. But shouldn't the left/right arrow keys be passed to the field editor?

Regards .. Subbu



--

The essence of object orientation is that objects collaborate  to achieve a goal.
Trygve Reenskaug      mailto: trygver at ifi.uio.no [mailto:%20trygver at ifi.uio.no]
Morgedalsvn. 5A       http://folk.uio.no/trygver/ [http://folk.uio.no/trygver/]
N-0378 Oslo             http://fullOO.info [http://fullOO.info]
Norway                     Tel: (+47) 468 58 625
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200612/66725472/attachment.html>