No, I just made the button prettier.  I like the click on board/show message 
action.

Max, I'm not sure how you can accidentally click on the board often (when the
computer is thinking)?

In general a user might not be sure what is happening and clicking the board and
nothing happening isn't the best answer.  Maybe the message could be improved to
something like, "The computer is thinking, interrupt the current process?".

Jon

Christian Anthon wrote:
> I assume that this is caused by Jon's latest changes to the stop
> button. Can you confirm that? Jon?
> 
> Christian.
> 
> On Mon, Jul 13, 2009 at 6:00 PM, Massimiliano
> Maini wrote:
>> Christian Anthon  wrote on 13/07/2009 17:48:43:
>>
>>> On Mon, Jul 13, 2009 at 3:17 PM, Massimiliano
>>> Maini wrote:
>>>> Hi,
>>>>
>>>> I just realized that clicking on the board while gnubg is thinkingon a
>>>> move
>>>> now pops up a dialog "Interrupt the current process ? OK/No".
>>>> Not sure it has always been like this. Anyway, proabbly not a good idea.
>>>>
>>> Debatable I guess. What action would you like gnubg to take in this
>>> case? Personally I find it very frustrating when you interact with a
>>> busy program that replies by doing nothing in return (or beeps).
>> Debatable indeed. Maybe it was just me being unaccustomed to it, but it
>> happened a lot to click by mistake and get the dialog, very annoying.
>>
>> The fact gnubg is "alive" is shown by the spinning hourglass.
>> In case you really want to stop gnubg thinking, there's the stop button.
>> I suspect this action (stop gnubg) is used on rare occasions.
>> Hence I would prefer no action for any click when gnubg is thinking, except
>> for clicks on the stop button.
>>
>> MaX.
>>
> 
> 
> _______________________________________________
> Bug-gnubg mailing list
> [email protected]
> http://lists.gnu.org/mailman/listinfo/bug-gnubg
> 
> 




_________________________________________________________________
With Windows Live, you can organise, edit, and share your photos.
http://clk.atdmt.com/UKM/go/134665338/direct/01/
_______________________________________________
Bug-gnubg mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnubg

Reply via email to