Could not retreive value from betBoxRef

[GoogleCodeExporter]

I'm now playing around with the increase and decrease betting amount, but I 
always get this:

2009-12-30 22:27:47.158 BlazingStars[7187:a0f] inClick:  
x=650.940002,y=498.552002
2009-12-30 22:27:47.159 BlazingStars[7187:a0f] x=650.940002,y=498.552002
2009-12-30 22:27:47.160 BlazingStars[7187:a0f] Could not retrieve value from 
betBoxRef!
2009-12-30 22:27:47.160 BlazingStars[7187:a0f] Got betsize: -1
2009-12-30 22:27:47.161 BlazingStars[7187:a0f] Trying to get blind size.
2009-12-30 22:27:47.163 BlazingStars[7187:a0f] Small blind: 15  Big blind: 30
2009-12-30 22:27:47.163 BlazingStars[7187:a0f] Game type: Tournament
2009-12-30 22:27:47.164 BlazingStars[7187:a0f] amountToChange: 1  bigBlind: 30  

In the end, I always end up with 29 in the bet box... Anyone seeing this as 
well?

Original issue reported on code.google.com by luca.hel...@gmail.com on 30 Dec 2009 at 9:31

[GoogleCodeExporter]

Hmm.  I can't replicate this on the main PS client, so if it's replicable, then 
it
has to be something to do with the IT client (or something on your machine, 
Luca). 
Could you try buying in short to a play money and using another hot key that
interacts with the bet box, like the pot size bet keys, or the all-in key?  If 
those
*don't* fail, try changing your hotkey choices for the increase / decrease key 
and
re-trying?  

What *are* your hotkey choices for increase / decrease?  I had some troubles 
with a
couple choices, like up and down arrows, previously.  I've ironed these out on 
the PS
client (as far as I know), but the IT client might be popping those same 
problems up
again.

Original comment by steven.h...@gmail.com on 31 Dec 2009 at 12:10

[GoogleCodeExporter]

I'll try to figure this one out too... my machine seems cursed... :( 

All pot size bet keys work properly now, including the all-in key. The only 
ones that fail 
are the ones for the increase/decrease keys. I tried 8 different combinations 
(, .) (m n) 
(- +) (1 2) and all gave the same result. I'll try to understand what's going 
on with gdb 
in the afternoon.

Original comment by luca.hel...@gmail.com on 31 Dec 2009 at 11:39

[GoogleCodeExporter]

Hmm.  I just saw this while I was working on the pot sized betting code.  Luca, 
are
you (or were you) using the Hyper-Simple theme?  It's the only theme I've seen 
it on.

Original comment by steven.h...@gmail.com on 5 Jan 2010 at 8:16

[GoogleCodeExporter]

Steven, it happens to me on all themes, unfortunately. 
gdb tells me that "value" is zero, no matter what, which triggers the error... 

if (!value || err != kAXErrorSuccess) {
        NSLog(@"Could not retrieve value from betBoxRef!");
        return -1;
}

This leaves me with no clues...

Original comment by luca.hel...@gmail.com on 5 Jan 2010 at 10:43

[GoogleCodeExporter]

Luca,

By way of explanation:  to get the value of the current bet, as shown in the 
bet box
(i.e. if you're currently betting $0.25, it shows up in the box in the bottom 
right
next to the bet size slider), BlazingStars has to the use the Cocoa 
Accessibility API
to get the window element at a certain mouse position.  (The other way is to 
search
the accessibility hierarchy, but I seem to remember that the bet box doesn't 
show up
that way). This is a clumsy solution, but it's the only one I've got right now. 
Possible reasons for the error you're experiencing:

1).  Something is different in the PokerStars.IT client, say in the position of 
the
bet box or in the programming of the client itself.  Unfortunately, I can't 
directly
test this because I don't have an account on PokerStars.IT. I'm going to talk 
to them
to see if I can get a test account or a second account.
2).  There is some program running on your system which is interfering with 
either
the Accessibility API or the mouse.  To test if something is mucking with the 
API,
you could try turning off the API and seeing if one of your programs starts
complaining.  You can find it under System Preferences->Universal 
Access->"Enable
access for assistive devices". Turn that checkbox off, and see if anything
interesting happens.  (Note that when you do, BlazingStars will stop working as 
well;
you'll have to turn it back on to keep using your hotkeys).  
3).  Something I'm not thinking of. :-)

In the mean time, I've committed a change to the current SVN version which has 
much
more informative error logging for the method you're having a problem with.  If
nothing else solves the problem, could you download the latest trunk version and
report any new error information?

Thanks!

Original comment by steven.h...@gmail.com on 5 Jan 2010 at 10:32

• Changed state: Accepted

[GoogleCodeExporter]

The error I get now is:

2010-01-06 00:34:46.363 BlazingStars[14813:a0f] inClick:  
x=649.940002,y=498.552002
2010-01-06 00:34:46.363 BlazingStars[14813:a0f] x=649.940002,y=498.552002
2010-01-06 00:34:46.363 BlazingStars[14813:a0f] CopyElementAtPosition reports 
that the AXUIElementRef (appRef) is invalid! 
(kAXErrorInvalidUIElement)

You should be able to make an account on pokerstars.it, as long as you give an 
address in italy. You won't be able to withdraw any money, but you'll be 
able to play any freeroll and any play money game... 

I can make one up for you, and give you access to it (in a private email, 
maybe).

Let me know how you want to proceed... 

Original comment by luca.hel...@gmail.com on 5 Jan 2010 at 11:40

[GoogleCodeExporter]

Okay, wait, hang on, I think I might know what's going on.  I'm going to 
refactor
some code, and I'll get back to you in a little bit.

Original comment by steven.h...@gmail.com on 6 Jan 2010 at 12:42

[GoogleCodeExporter]

Luca, I think I may have nailed this down.  Give the latest commit a try...

Original comment by steven.h...@gmail.com on 6 Jan 2010 at 6:33

[GoogleCodeExporter]

I knew you deserved those beers... 

;-) 

You can set this to fixed. It is now working perfectly....

Original comment by luca.hel...@gmail.com on 6 Jan 2010 at 1:39

[GoogleCodeExporter]

Thanks for bearing with me while I figured this one out, Luca.  Sorry it took 
me so
long. :-)  On the upside, I talked to the Ps.IT people and they'll let me open 
a play
money account on the Italian site, so I should be able to test things more 
easily
from now on.

Original comment by steven.h...@gmail.com on 6 Jan 2010 at 6:39

[GoogleCodeExporter]

Original comment by steven.h...@gmail.com on 6 Jan 2010 at 6:40

• Changed state: Fixed