You must have your automove toggle set to on, jonesey.

help toggle-automove
Personally, I've never seen automove make a mistake, and I'd like to see an example of when it has.

Regarding ["pause for double" even in a crawford match.], all you have to do is toggle double.

help toggle-double
FIBS sets the doubling cube off in Crawfords and one-pointers, but you can turn it on again, like if you want to slow down a game with a bot so you can see what's happening.  This is an excellent time to point out that FIBS has comprehensive help files that are ignored by most GUIs.

At this point you might want to ask FIBS,

help toggle

'hope this helps!  Oh, and you might want to save your options.  See FIBS help files!

--
don

You're not the only one, jonesy, which perfectly makes my point that FIBS clients, wonderful as they are, could be made to interface better with FIBS:

• Clients can easily point to FIBS' in-depth online help;
• There's frequently confusion about how to send a command directly to FIBS;
• Some clients emulate FIBS commands internally, but differently from FIBS (FIBS is not going to change so clients should act like FIBS for the benefit of, and from the perspective of other FIBS users.).

--
don

Hey burper, ole_salt, aristoF, CantBuyAThrill, nutcracker, thefog, whatever other IDs you may have on FIBS.

In reply to your

I can only admit that I've had two versions of a Graphic User Interface (GUI) for FIBS that I've ever shared for comments or testing -- The first I used for about 10 years on FIBS, the second I'm working on, and  I freely confess that I've yet to come up with a GUI that I'd release to the general public.  I admire all of the programmers who have come up with complete programs to interface with FIBS.  I have not come up with anything for release.

I'm not sure if you understand computer programming, but I can tell you that there are two factors that are worth measuring, length of a program and I/O (input/output), that relate to difficulty of programming.  As the length of a program increases, so does it complexity by at least an order of magnitude.  Same same for I/O.  My point here is simply that nobody can do it all alone, perfectly.  I don't know if you've noticed, but there are programmers who use FIBSboard for suggestions for their clients.  There's a whole section of 'em!

Anyway, I've checked out most clients except for MacFIBS.  I've also watched users of all clients on FIBS, and I think my suggestions as a programmer are worth more than snide remarks.  I am making suggestions based on experience.  You seem to have a problem with my suggestion that:  No matter what a client does for its user, it should be transparent to other users.  In fact, this is obvious to me, but might be made clear by the following from http://http://www.fibs.com/fibs_interface.html#tell:

Note that there is some feedback expected from the FIBS protocol:

Therefore I think that clients should respond to the rest of FIBS with the same, instead of

This is a case where expected feedback to other users, not necessarily using the same GUI, get different results.  There are others.

For general purposes, I have no problem with this, but I hope you can see it could impede completion of, say, a tournament.  In fact, there is at least one user who thinks, using JavaFIBS, that any match communications between competitors should be referred to the TD.  In a tournament situation, I think communication should be clear between players, and therefore I think that GUIs should strive to emulate FIBS.

--
don

i can't read all that meandering drivel don.
all i can suggest is that you demand your money back.
if you like, you can complain to repbot about the authors and smite their karma here on fibsboard.

I think maybe you are right.     Thank you!   

socksey



"Most of us go to our grave with our music still inside of us." – Anonymous

Sorry to digress from the thread but:

don - please note burper is a fine programmer himself and I suspect that, as often, you've not recognised teasing. I hope I'm underestimating you there - your summary of two rather obvious guidelines for programmers (viz. do not repeat work already done; stick to standards of communication between different interfaces to the same environment) may well be  intended to tease burper by telling him something he's sure to know.

Steve / spielberg

PS whatever happened to zoeboy?

I made a programmable button in my javafibs for that very problem.  Whenever a newbie invites me, and I try to accept, but instead, get the regrettable message that tells me newbie hasn't invited me, I click my button which displays in shouts:

 "attention impatient newbies!  if you don't give someone time to respond to an invite, your next invite will cancel out the first.  remamber that we might be checking out your rep, so please give us time to respond.  ))"

The reason I made a button for this is because it happens so very frequently to me.   

You're right, don, it would be much nicer if this were explained or incorporated where it should be.     I'm sure veteran Fibbers get tired of my (almost spam) messages in shouts.      

socksey



"A person should not promise to give a child something and then not give it, because in that way the child learns to lie." - Babylonian Talmud