10-25-2013, 07:10 AM
I haven't tested this extensively, but if my guess is right, the problem isn't easily fixed. The stupid 888 site uses black buttons with only a shade of color at the bottom of the button. SaT uses a pixel near the bottom of the button to try to grab some color to use to detect if the Fold button is visible.
I asked for your table size because at smaller table sizes, perhaps the 888 buttons do not show enough color for SaT to grab it successfully. When SaT cannot grab the fold button color, it falls back on searching for the betbox. But when someone shoves all-in on you, the betbox isn't visible. So this would be symptomatic of your problem.
Please try this: create a new layout (File->New Layout) and use the default 888 table size as the base for your grid size. You can do this by using the tile or cascade function built into the 888 table, which will then resize the 888 table to the default size. Then go and include 888 as normal and set up your grid layout and then see if the tables will now correctly detect that action is required when someone shoves on you and you can only fold or call. If it works at the larger default table size, but fails on your smaller table size, then we can narrow the problem down.
I asked for your table size because at smaller table sizes, perhaps the 888 buttons do not show enough color for SaT to grab it successfully. When SaT cannot grab the fold button color, it falls back on searching for the betbox. But when someone shoves all-in on you, the betbox isn't visible. So this would be symptomatic of your problem.
Please try this: create a new layout (File->New Layout) and use the default 888 table size as the base for your grid size. You can do this by using the tile or cascade function built into the 888 table, which will then resize the 888 table to the default size. Then go and include 888 as normal and set up your grid layout and then see if the tables will now correctly detect that action is required when someone shoves on you and you can only fold or call. If it works at the larger default table size, but fails on your smaller table size, then we can narrow the problem down.
