Full Tilt Shortcuts - new ahk script

[beaster]

[ QUOTE ]
Nano,

I'm having some trouble with the latest version (0.55). It keeps trying to reload all of my tables constantly, even if I'm above the max. buyin. The auto-reload did not work at all on the previous versions, I would have to use the manual reload feature. The reload window will now come up on all of my tables, and even if I close it, it will just open up again.

I'm gonna probably just stick to the version you released just before this last one, but just wanted you to know I was having trouble with the newest one.

Thanks.

[/ QUOTE ]

Yeah, having the same problem. Deal me in works now, and auto reload KIND OF does...but the problem is auto reload keeps reloading even when it doesn't need to. This version is an improvement over the last one though.

[mttsemipro]

Using Vista i set to classic theme and downloaded v0.55 and now everything is working great. 12 tabling is effortless and its paying of great. Many Thanks Nano.

[nanochip]

[ QUOTE ]
[ QUOTE ]
Nano,

I'm having some trouble with the latest version (0.55). It keeps trying to reload all of my tables constantly, even if I'm above the max. buyin. The auto-reload did not work at all on the previous versions, I would have to use the manual reload feature. The reload window will now come up on all of my tables, and even if I close it, it will just open up again.

I'm gonna probably just stick to the version you released just before this last one, but just wanted you to know I was having trouble with the newest one.

Thanks.

[/ QUOTE ]

Yeah, having the same problem. Deal me in works now, and auto reload KIND OF does...but the problem is auto reload keeps reloading even when it doesn't need to. This version is an improvement over the last one though.

[/ QUOTE ]

I guess on the right track, but still not there.

The auto-reload is dependent upon reading the hero's stack size correctly (which can be seen in the debug tooltip).

Could tell me what happens if you enable debug mode (misc tab), and tell me how often and when the Hero's stack number is wrong.

Another clue is the HeroStackX and Y should give the coordinates of the hero's stack on the window. If you could check that position using Window Spy (included with AutoHotKey) and tell me where the X and Y are in relation to the stack numbers. The X and Y should be to the left of the hero's stack (near the left edge of the player's black box) and approximately aligned with the top of the stack numbers.

Also tell me the TitleBarH and TableW,H from the debug window.
Thanks,
nano

[beaster]

[ QUOTE ]

Could tell me what happens if you enable debug mode (misc tab), and tell me how often and when the Hero's stack number is wrong.

Another clue is the HeroStackX and Y should give the coordinates of the hero's stack on the window. If you could check that position using Window Spy (included with AutoHotKey) and tell me where the X and Y are in relation to the stack numbers. The X and Y should be to the left of the hero's stack (near the left edge of the player's black box) and approximately aligned with the top of the stack numbers.

Also tell me the TitleBarH and TableW,H from the debug window.
Thanks,
nano

[/ QUOTE ]

According to the debug tooltip, the stack appears correct at most times. Occasionally it goes to ? but that might have been because I was switching applications while testing.

TitleBarH=21, TableW,H=802,576

HeroStackX,Y=353,504. These coordinates correspond to the brown X in my screenshot below, which is where it should be according to your descriptions.


Playing on 1 table for ~10 minutes, the stack auto reload appeared to work ok. Will let you know later how it goes when I get a chance to multitable.

BTW, I'm using 0.56.

[Powers_That_Be]

Now that this is full fledge shareware, any chance of adding some ICM info into those tool tips. Could be really helpful in a SNG to have some realtime calculations.

[nanochip]

[ QUOTE ]
Now that this is full fledge shareware, any chance of adding some ICM info into those tool tips. Could be really helpful in a SNG to have some realtime calculations.

[/ QUOTE ]
I've thought about that one too. I'm not up to speed on all the math behind the calculations, and I haven't seen it clearly explained anywhere. If you have any sources, I'd be interested in seeing them.
nano

[beaster]

Some additional data -- the auto reload seems to function correctly when 1-tabling...but 5+ tables and it goes haywire. Keeps reloading even when not necessary.

[nanochip]

[ QUOTE ]
Some additional data -- the auto reload seems to function correctly when 1-tabling...but 5+ tables and it goes haywire. Keeps reloading even when not necessary.

[/ QUOTE ]
I just did 30 minutes of playing with 4 tables, and didn't see anything unusual with auto-reloading (par for this course).

Does the hero stack numbers always seem right in the debug tooltip? As you move your mouse around the tables you have open it should update the stack number in about a second.
Of course the stack number will disappear when it disappears from the table (when it says things like "check" instead).
Let me know any other clues you see...
Are all of your tables visible, without overlap of the hero's stack area?
What setting do you have for the reload amount? Does it mess up if you use 98 (my usual setting)?
Do you ever see more than one "get chips" dialog box open? The code is not supposed to open more than one.

I would guess that this problem is still related to reading the stack size correctly, but if it always looks right in the debug tooltip, that would discount that idea.

Thanks again for your good/informative clues. Debugging by proxy is difficult.
nano