bustiiing / blazingstars

Automatically exported from code.google.com/p/blazingstars
0 stars 0 forks source link

Auto Time Bank function #31

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
In the most current release (.9.8) the auto time bank feature doesn't appear to 
be working. I'm 
getting the same results I saw in the previous build released on the developer 
site fully functional 
software. Playing multiple tables in cascade view using the pokerstars black 
theme. 

I'm guessing this works for you Steve. Might I ask what conditions this works 
under? 

Original issue reported on code.google.com by amar...@gmail.com on 15 Jan 2010 at 7:07

GoogleCodeExporter commented 8 years ago
Initially, I saw no problems w/ the ATB feature, but I'm now noticing occasional
failures; I'm using black theme and title configuration. I've had three
non-activations over the last 48 tournaments.

Original comment by vyo...@gmail.com on 16 Jan 2010 at 5:37

GoogleCodeExporter commented 8 years ago
I'm going to actually sit down and play some actual *poker* any day now, so 
that I
can test this out myself and see what the limitations are right now.  Anyone 
looking
at this, please give 0.9.8 build 21 a try and let me know if that helps or if 
you're
still having problems here.

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

GoogleCodeExporter commented 8 years ago
Here's a comment that Andrew sent in; I'm posting it for him because he can't 
seem to
post to Google Code issues right now:

I probably should have tested this out on play money tables or something but 
decided
to give it a go while playing a bunch of my regular buy ins yesterday. I've had 
to
disable the auto time bank function because I ran into some problems. I'm not 
sure if
this can be changed and maybe this feature just doesn't suit someone like me 
but this
is what happens...

I'll be playing around 15 tables and suddenly get distracted or have to think 
for
more than a couple seconds about a decision. Tables in the background begin 
telling
me it's my turn to act, and eventually the time bank option will pop up on said
tables. BlazingStars will jump from the currently active table to the table at 
which
a new time bank action has popped up and click it. So, it is performing its 
job, but
it's also jumping away from the table that I have the least amount of time to 
act on.
This then resulted in a kind of domino effect and I was left timing out on 
quite a
few tables. 

If I'm not being clear let me know. In my limited use of Table Ninja (if I'm not
mistaken) the auto time bank feature would somehow click the "time bank" button
without having to switch to the window in the foreground. No idea how this 
done, but
if I remember correctly it did this somehow. 

Original comment by steven.h...@gmail.com on 20 Jan 2010 at 5:36

GoogleCodeExporter commented 8 years ago
I think I might understand the problem now;  thanks, Andrew, for the detailed
description.  The way I've currently implemented the feature, the window *must* 
be
brought to the foreground.  If I am going to send clicks to windows in the
background, I'm going to have to do some much lower-level hacking, including 
using an
API which *may* be undocumented
(http://stackoverflow.com/questions/726952/simulate-mouse-click-to-window-instea
d-of-screen).
 It seems like it might be possible, but it's going to take me a couple of days to
implement, so give me some time to try implementing it the way you want.

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

GoogleCodeExporter commented 8 years ago

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

GoogleCodeExporter commented 8 years ago
Okay, I've spent nearly two days on this, to no avail.  Every method I can come 
up
with ends up bringing the window into the foreground, including using the 
CGWindow
APIs.  Unless I can find another way to do this, the time bank feature is either
going to have to remain as it is, or be removed if it doesn't meet user 
desires. 
I'll try asking around, but it's looking more and more like I can't fix this.  
<sigh>

Original comment by steven.h...@gmail.com on 21 Jan 2010 at 7:54

GoogleCodeExporter commented 8 years ago
Please see issue 44 for further discussion of this problem.

Original comment by steven.h...@gmail.com on 28 Jan 2010 at 5:09