New Software SpadeEye: Tableselection (@PP)

[PatInTheHat]

I have been trying to get the trial version going however whenever I run the .exe file nothing happens and SpadeEye never opens.

Any help Mr Snood?

[Mr_Snood]

Delete the file "db.conf" from your SpadeEye installation directory and try again.

If this don't help then email me ( Support@Spadeit.com ) the file "log.txt" which is also in your SpadeEye directory,
so i can make further investigations.

[timtowdi]

Mr. Snood, sorry for the bother as I know you have a ton of things on your plate, but I was wondering if you can add the functionality to close out empty stars tables once they've died. I've been trying to create an .ahk version which simply hits OK everytime a window pops up saying "This table has been closed" but am not sure how to handle the different table names when trying to activate the window.

Thank you.

[timtowdi]

nevermind, realized this isn't necessary. Thanks for a great product.

[timtowdi]

One thing I thought might be useful, if there is an option to skip a specified # of tables for your stars opener so that it doesn't open all the empty tables (and continuously reopens them) as it starts traversing from the top of the list.

Thanks!

tim

[kidpokeher]

Hi Mr. Snood,

Just downloaded your update. I don't know if you intended this but the update contains a new db.conf file. Once we replace this file, we have to reset our databases. In addition, once we get an error message we cannot do a full scan without restarting SpadeEye, even if we set a correct database. It seems to grey out the Full Scan option.

Even more troublesome, if we switch from one client to another the Full Scan option remains greyed out until restarted.

Also, the latest update seems to have difficulty scanning FT tables. This happens with earlier versions as well. I've tried to figure out what causes SpadeEye to skip some tables during a full scan. It may be coincidence, but I've noticed that the time tables are skipped (no players appear in the scan) *seem* to be the times FT takes longer than normal to pull up the list of players on the selected table. In other words, I think SpadeEye is skipping the table because the players aren't loaded in the FT poker client yet. Meanwhile, SpadeEye is already moving to the next table on the list. Just a guess.

[Mr_Snood]

Hi kidpokeher.

Thanks for the feedback.
The problem with the db.conf file is the following:
The format of the file has changed.
So if a new SpadeEye version tries to load an old db.conf-file it crashs.
Thats why i put an empty db.conf file into the upgrade.zip.
I will put a remark on the downloadpage to explain the problem.

The "Full Scan greyed out problem" is new to me.
What is the initial client set?
From which to which client are you switching that the FullScan remains greyed out? No matter from which to which?
Nevertheless now that i know about this i will take a closer look.

My guess about the FT scanning is that either (as you said) the FT client did not respond with a playerlist within 3 seconds,
or that the client updated the tablelist during the scan so that the roworder has changed.
For example table #15 became table #14 (because a tables was removed).
In such a case SpadeEye may skip a table because it moves the tables by roworder...

[Mr_Snood]

Is no problem i will add it.

[thac]

Sorry if this has been asked, but can you put a rough stack size of the players when you scan the tables? Something rough like this when you click on the tables

Screenname BBs Buddy Autorate ..
A ............ 100
B ............ 85
C ............ 145
D ............ 30
E ............ 55

[hoosiertim]

I would like to be able to scan a specific limit or limits and then list every player at that limit by VP$P% ( or other data) The old table selection software I used back in the day at Party could do this. Could you include it in the next update?