Yeah obviously this would be a problem!
Can you give a bit more details? How many tables are you playing on? What Tile Setting? What Scan Mode? Does this happen with only certain sites? Does it happen only with mouse clicks, or with hotkeys too?
Do you notice on these occasions if the next table underneath requires action or not? Perhaps when this happens, the action tries to get sent to the next table underneath, but since it doesn't require action, no buttons are there to be pressed. So I wonder if this is really the same problem as the misclick. From what I can gather, you are clicking on a button, the table is moving to the grid before the actual action is sent, and the action ends up being sent to the table underneath?
Engine delay simply is how long it waits between scanning the tables. This probably doesn't matter, and its likely I'll remove it.
Action delay is how long to wait AFTER sending the action to the table, and then table moves (either to stack or grid). This MIGHT help, to try increasing the delay.
I'm going to bed now but I'll check back tomorrow
Can you give a bit more details? How many tables are you playing on? What Tile Setting? What Scan Mode? Does this happen with only certain sites? Does it happen only with mouse clicks, or with hotkeys too?
(07-11-2011, 04:19 PM)soulsbyc Wrote: Sometimes when I click call/raise on a game in the stack it moves to the grid, but the action is not sent. This is not too much of an issue as I just have to click raise/call again on the table when it is in the grid.
Do you notice on these occasions if the next table underneath requires action or not? Perhaps when this happens, the action tries to get sent to the next table underneath, but since it doesn't require action, no buttons are there to be pressed. So I wonder if this is really the same problem as the misclick. From what I can gather, you are clicking on a button, the table is moving to the grid before the actual action is sent, and the action ends up being sent to the table underneath?
(07-11-2011, 04:19 PM)soulsbyc Wrote: Can one of the advanced settings help with this?
I am not sure what action delay and engine delay do.
Engine delay simply is how long it waits between scanning the tables. This probably doesn't matter, and its likely I'll remove it.
Action delay is how long to wait AFTER sending the action to the table, and then table moves (either to stack or grid). This MIGHT help, to try increasing the delay.
I'm going to bed now but I'll check back tomorrow
