Originally Posted by Mr_Snood
Maybe your database settings in the new SpadeEye got lost (main->options->databases)?
This sounds pretty complicated and i am not sure what such a function is good for.
Isn't the aim of a tableselection tool to find the best available tables?
Why constrain on the open tables?
Thanks, my db wasnt listed correctly.
The function i thought of was this- lets say there are 30 open tables, and we are datamining 12 of them. If we arnt playing, we dont care how long scans take.
Lets say, though, we are playing 3 tables, and in the waiting list for another 6. We want our stats to be up to date, so a 'mini scan' of just those tables that are open would be very nice. It wouldnt take up much time (or cpu), and we can check that mr fishy is still on our table when we are to sit down
Also, it can be hard to find what tables we are actually on. If we are on three, and there are thirty tables, and we are trying to find a certain stat on a player (ie do we call a big river bet and want to see won$ at sd%), it is almost impossible to find the table we are on, then the player, and then the stat.
If we could have a little checkbox, so that only the open tables were on the screen, this would be very helpful. As soon as we uncheck, we go back to the normal screen, and the big long scan