Re: GtkButton and double clicks

Tim Janik wrote:
On Thu, 16 Sep 2004, Federico Mena Quintero wrote:

I'm pretty sure this has been discussed before, but I couldn't find

Right now, double-clicking on a GtkButton gives you two emissions of the
"clicked" signal.

This is bad for things like launcher buttons in the Gnome panel.  People
get confused all the time, double-click on them because that's what they
think they have to do to open a program, and get two instances of the
program rather than just one.

Do we need an API like

	void gtk_button_set_ignore_double_click (GtkButton *button,
						 gboolean   ignore);
	gboolean gtk_button_get_ignore_double_click (GtkButton *button);

(and the corresponding property)?

If so, should we turn it on by default?  I *think* there are not many
buttons which you want to be able to click rapidly/repeatedly.

i think that is a good idea. clicking on a panel launcher twice by
accident happends to me once in a while after i've been mousing around
with nautilus in double click mode for too long ;)
and i'd even opt for ignoring double clicks by default, since the
scenarios where double clicks on buttons are really needed (e.g. "Fire"
in a game, or triggering a filter slide in a synthesis application) are
rare enough, that i don't expect actual harm as long as the new behaviour
is properly documented as an incompatible change between releases and the old
behaviour can be restored (gtk_button_set_ignore_double_click).

It would be useful to have a "double-clicked" signal built into relevant
widgets, and have the double-click time interval settable from somewhere
such as .gtkrc or with something like gtk_widget_set_doubleclick_interval().
I currently do this stuff with a thread and async queue.

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