![]() |
|
#101
|
|||
|
|||
|
[ QUOTE ]
That's weird. It's working fine for me. I can't explain any of the things you mentioned right now... likely all part of the same problem though [/ QUOTE ]I added a bunch of bits for writing-down the %which_limit% and %which_game% in the .ini. That's why they weren't saving. This hasn't fixed all the bugs, though. I'm still loading the wrong limit more often than not, regardless of stopping and going. [img]/images/graemlins/frown.gif[/img] -Sam |
|
#102
|
|||
|
|||
|
[ QUOTE ]
Damn. Can you try using SetKeyDelay to see if maybe it just can't handle the speed? I can't think of anything else right now... [/ QUOTE ]I don't think that's it. We're doing almost exactly the same thing to find the tables as we're doing to find the limit, and the tables work fine. I'll get deeper into it and let you know how it goes. -Sam |
|
#103
|
|||
|
|||
|
Let's see... it's actually pretty simple. First thing it does is click the "T" button (for tourneys); then it clicks the "C" button. This should close all the trees.
Then it sends {UP} 7 times which ensures we get to the topmost tree. Then it sends "which_game - 1" {DOWN} keys; for hole'em "which_game" is 1, so it sends zero down keystrokes. Then it sends {Right} once to open the tree and then "which_limit" down keystrokes. I don't really see how this could go wrong, but obviously it does... Have you tried the work-around with SetKeyDelay? |
|
#104
|
|||
|
|||
|
Im retarded with computers but all this stuff seems really neat. Could someone tell me what this is and when it will be available?
|
|
#105
|
|||
|
|||
|
[ QUOTE ]
Let's see... it's actually pretty simple. First thing it does is click the "T" button (for tourneys); then it clicks the "C" button. This should close all the trees. Then it sends {UP} 7 times which ensures we get to the topmost tree. Then it sends "which_game - 1" {DOWN} keys; for hole'em "which_game" is 1, so it sends zero down keystrokes. Then it sends {Right} once to open the tree and then "which_limit" down keystrokes. I don't really see how this could go wrong, but obviously it does... Have you tried the work-around with SetKeyDelay? [/ QUOTE ] It looks like it's not going all the way to the top before descending %wl%-1. I dunno. I'll keep fiddling. -Sam |
|
#106
|
|||
|
|||
|
[ QUOTE ]
It looks like it's not going all the way to the top before descending %wl%-1. I dunno. I'll keep fiddling. -Sam [/ QUOTE ] Nah, this can't happen. If it looks like that, it isn't closing all the trees most likely. I mean, if the tree was closed it simply has to start at the top. |
|
#107
|
|||
|
|||
|
[ QUOTE ]
Im retarded with computers but all this stuff seems really neat. Could someone tell me what this is and when it will be available? [/ QUOTE ] It's available right now. Obviously there are still bugs and stuff but it seems to be working for most ppl. Just click on one of the links (there somewhere in the first part of this thread) and you should be okay. |
|
#108
|
|||
|
|||
|
[ QUOTE ]
First thing it does is click the "T" button (for tourneys); then it clicks the "C" button. This should close all the trees. [/ QUOTE ][ QUOTE ] ControlClick, AfxWnd4210 ControlClick, AfxWnd429 [/ QUOTE ] On my WindowSpying, these clicks are going to "All" and then "Cash". -Sam |
|
#109
|
|||
|
|||
|
[ QUOTE ]
[ QUOTE ] First thing it does is click the "T" button (for tourneys); then it clicks the "C" button. This should close all the trees. [/ QUOTE ][ QUOTE ] ControlClick, AfxWnd4210 ControlClick, AfxWnd429 [/ QUOTE ] On my WindowSpying, these clicks are going to "All" and then "Cash". -Sam [/ QUOTE ] Problem soved most likely. We must be running different versions of PP? Mine says 91/91. I should change the code to check for text I guess. These updates are a pain. |
|
#110
|
|||
|
|||
|
[ QUOTE ]
Im retarded with computers but all this stuff seems really neat. Could someone tell me what this is? [/ QUOTE ]This is actually an elaborate ploy for Roland and me to get our post-count up. That's why we make dozens (of dozens) of posts that should really be PMs. [img]/images/graemlins/blush.gif[/img] In all seriousness, you can get the latest version here. About when it'll be ready, it'll probably be considered out-of-beta pretty soon. Because this thread is so damn long, I'll probably make a real announcement in a new thread when we're ready for prime-time. Till then, feel free to play around and tell us when (if!) stuff breaks. -Sam |
![]() |
|
|