10-26-2012, 02:46 PM
Thanks for your detailed response, this helps eliminate a lot of possibilities.
One thing I need clarity on.. initially you said that the 'lost' table is neither in the stack nor the grid. But then when you click on its icon in the taskbar, then it DOES pop into the grid. But on this last post, if I understand correctly, the table IS in fact in the grid, just not visible for some reason. . SaT has it listed as a "Tiled Table" on the main window tab, and that its slot gets passed over and unused by other tables needing action. So it seems that you are saying that the table is in fact tiled in the grid, but just minimized for some reason.
My original hunch was that the table was stacked within SaT, and that SaT was failling to recognize that it needed action (This will always fail when a table is somehow minimized). But then the act of restoring it to full size allows SaT to then see it again, and then instantly moves it to grid. Thats why I asked what might happen if you stopped SaT BEFORE restoring the table by clicking its icon.
One time when I was helping a user, he also had his stack partially off screen, and the part of the table that was offscreen included the fold/call/bet buttons. And tables weren't getting detected as needing action. When he rearranged it so that those were visible, SaT did start correctly detecting it. This was completely new to me because I am certain that I had tested it in the past where an offscreen stack slot still worked fine and that SaT would still detect action. But for this user, it didn't work. So maybe that is another thing to test just to see if that is the issue or not.
One thing I need clarity on.. initially you said that the 'lost' table is neither in the stack nor the grid. But then when you click on its icon in the taskbar, then it DOES pop into the grid. But on this last post, if I understand correctly, the table IS in fact in the grid, just not visible for some reason. . SaT has it listed as a "Tiled Table" on the main window tab, and that its slot gets passed over and unused by other tables needing action. So it seems that you are saying that the table is in fact tiled in the grid, but just minimized for some reason.
My original hunch was that the table was stacked within SaT, and that SaT was failling to recognize that it needed action (This will always fail when a table is somehow minimized). But then the act of restoring it to full size allows SaT to then see it again, and then instantly moves it to grid. Thats why I asked what might happen if you stopped SaT BEFORE restoring the table by clicking its icon.
One time when I was helping a user, he also had his stack partially off screen, and the part of the table that was offscreen included the fold/call/bet buttons. And tables weren't getting detected as needing action. When he rearranged it so that those were visible, SaT did start correctly detecting it. This was completely new to me because I am certain that I had tested it in the past where an offscreen stack slot still worked fine and that SaT would still detect action. But for this user, it didn't work. So maybe that is another thing to test just to see if that is the issue or not.
