Re: entry signals




Steve Hosgood <iisteve@iiweeble.swan.ac.uk> writes:

> > "If we want to catch when the user has entered text, we can connect to
> > the activate or changed signal.
> > Activate is raised when the user hits the enter key within the Entry
> > widget. Changed is raised when the text changes at all, e.g. for every
> > character entered or removed". 
> > 
> 
> Would it not be more logical for 'entry' to raise a "value-changed" signal
> for when the user hits the enter key?
> 
> I can understand the idea of "activate" for (say) check-boxes or radio-
> buttons, but not for this one. Is it not fair to think that "activate"
> should be equivalent to a "value-changed(to TRUE)" signal?

There is nothing necessarily changed when the user hits the enter
key. I can go into an empty and hit the enter key without modifying
anything, and I'll still get an ::activate signal.

The idea of the activate signal is "The user says do something with
this entry", that's all.

(Randomg sidenote, "activate" also exists for GtkText widgets -
 currently bound to Ctrl-Enter.)

Regards,
                                        Owen



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]