[pygtk] which widget

[Leon Bogaert]

Hi Robert,

Thanks! It's difficult to decise how the user should be "alerted" of the fact the input isn't valid. I was looking for an app that does rouglly the same. But I only found one and that implementation doesn't really work well :)
A colleague of mine does some interface designing occasionally. I think I'll ask him tomorrow how he thinks about that.

Regards,
Leon

________________________________________
From: admin at exolucere.ca [admin at exolucere.ca] on behalf of Robert Park [rbpark at exolucere.ca]
Sent: Thursday, December 02, 2010 19:03
To: Leon Bogaert
Cc: pygtk at daa.com.au
Subject: Re: [pygtk] which widget

On Thu, Dec 2, 2010 at 12:16 AM, Leon Bogaert <leon at tim-online.nl> wrote:
> Yeah, but how should I for it to always be on the entries in the ListStore? Because now one can type anything in the combobxEntry. A user could type something, ignore the suggestions and move the focus to another widget. How should I deal with this situations? For example, an on_update handler which checks if the entry in the comboBoxEntry exists in the liststore. If it doesn't exist: remove the entry. But that doesn't seem really user friendly.

Well, your signal handler will know what value the user has typed.
Simply check if that value exists in your liststore, and if it
doesn't, there's any number of things you could do. You could: refocus
the combobox when the user tries to focus away from it, discard any
invalid entry the user has typed, display an error dialog instructing
the user to type something else instead.

You just have to be careful to balance your need to have the input
validated with the users need to not be overly hassled with cumbersome
restrictions on their interaction with the program.

--
http://exolucere.ca