Oh ok I think I understand you.
Well, SaT first checks the size of the table. And if the size is correct, then it doesn't do anything. But if the size is wrong, then it will attempt to resize the table. That is how its supposed to work anyway.
I just tested it. Yes, when you close a table, Winamax 'saves' the size of the table and opens up all new tables that same size. And then SaT doesn't try to resize those.
What version of Windows are you using? And in the Included Sites listbox in SaT, does it say "Winamax" or "Winamax_Small" ?
You could try this (use Winamax instead of OnGame):
Does that make sense?
Let me know if it works
Well, SaT first checks the size of the table. And if the size is correct, then it doesn't do anything. But if the size is wrong, then it will attempt to resize the table. That is how its supposed to work anyway.
I just tested it. Yes, when you close a table, Winamax 'saves' the size of the table and opens up all new tables that same size. And then SaT doesn't try to resize those.
What version of Windows are you using? And in the Included Sites listbox in SaT, does it say "Winamax" or "Winamax_Small" ?
You could try this (use Winamax instead of OnGame):
http://www.stackandtile.com/sat/help/ongame Wrote:When you start your session, only open up ONE OnGame table and let SaT resize it. Then, CLOSE the table. When you close the table, the OnGame software will 'remember' that table size and open up all new tables the same size by default, so that SaT will not need to resize them, since the OnGame client will do it.
Does that make sense?
Let me know if it works
