[sfi]

johnu, on 2015-August-26, 22:24, said:

Can't you send a message to the table if you don't know who is causing the delay?

Sure there are ways within the interface to deal with this, but they are clunky if you don't know where the delay is.

[1eyedjack]

johnu, on 2015-August-26, 22:24, said:

Can't you send a message to the table if you don't know who is causing the delay? Or use a voice app?

Yes potential solutions abound. As with all suggestions and counter-suggestions of this type, it is all down to whether the cure is worse than the disease.

[barmar]

1eyedjack, on 2015-August-27, 01:23, said:

Yes potential solutions abound. As with all suggestions and counter-suggestions of this type, it is all down to whether the cure is worse than the disease.

Or, from our perspective, whether the benefit is worth the effort to implement it, and the extra clutter in the user interface to accomodate it (like table options).

Sometimes we implement infrequent options using special keywords in the table notes, instead of a visible option in the table settings, to avoid adding more complexity. But this means that most people won't know about it, so we have to balance complexity with memorability.

Nothing is as simple as it seems, there are lots of details that aren't obvious.

[btour]

You take inferences from delay at your peril. What I think would help is that the last card played does not disappear so quickly. That gives on time to see it and not have to replay the trick constantly.