> Let me sum up:
> * In the beginning of each button click callback you call a
> function to make the buttons insensitive (even the clicked one?
> protection is needed here also),
I just kept a list of all the buttons that mattered, and insensitised them all
rather indiscriminantly (even the cli
Am Fr, den 11.02.2005 schrieb Felix Kater um 22:09:
> Iago Rubio:
>
> > Set the window insensitive - or the buttons - and use a wait cursor to
> > tell the user the program is working and should not be disturbed :)
>
> Thanks, this is, however, no solution. The problem is harder than it
> seems i
Freddie Unpenstein:
> How about clearing the button blocked flag from an idler, started once
> the action is complete?
[...]
> All I'd need to deal with your situation, would be to slip in
> an idle timeout to call the restore function instead of calling the
> restore function directly. That's
Iago Rubio:
> Set the window insensitive - or the buttons - and use a wait cursor to
> tell the user the program is working and should not be disturbed :)
Thanks, this is, however, no solution. The problem is harder than it
seems in the beginning: Whatever you do/block/change inside the button's
On Thu, 2005-02-10 at 02:16, Felix Kater wrote:
> Hi,
>
> in my app some actions behind buttons take time, so the button is
> released not before the action is done. This is ok.
>
> However, I need to prevent the user from clicking other buttons in the
> meantime.
Set the window insensitive - or
> in my app some actions behind buttons take time, so the button
> is released not before the action is done. This is ok. However, I
> need to prevent the user from clicking other buttons in the
> meantime. The problem seems to be harder than it looks since gtk
> can not empty the mouse click buf
