Closed GoogleCodeExporter closed 8 years ago
Do you mean pressing the "Check" button in the "Checking is free" popup?
Original comment by steven.h...@gmail.com
on 15 Jan 2010 at 7:37
Andrew,
I've checked in a fix for this, or at least what I think the issue is :-). The
"check" button is now pressed; my solution is a little inelegant, so I hope
there
isn't another popup window with "PokerStars" as the title and a Check button in
the
middle that I just couldn't find, but there you have it! You'll see it in the
next
release.
Original comment by steven.h...@gmail.com
on 15 Jan 2010 at 8:24
Original comment by steven.h...@gmail.com
on 15 Jan 2010 at 8:24
There is another one. If you click the close button in an active tournament,
BlazingStars will automatically close
the tournament. :o
Original comment by derk.b...@gmail.com
on 17 Jan 2010 at 3:48
I'm recovering from a bout of food poisoning, so I know I'm a little fuzzy, but
i'm having trouble
understanding. Can you be a little more specific?
Original comment by steven.h...@gmail.com
on 17 Jan 2010 at 3:56
If you are playing in a tournament, and you close the tournament table a popup
will appear saying something
like "If you leave the table you will be 'Sitting out'" and there are two
buttons: Close and Cancel. BlazingStars will
autoclick the Close button.
Original comment by derk.b...@gmail.com
on 17 Jan 2010 at 6:43
derk.bell,
I took a look (who knew that PS had play-money SNGs? That'll make my life a
little
easier!), and the reason that BlazingStars will auto close the table is because
the
popup is functionally the same as for leaving a cash table (especially since the
buttons are . Is this something that really needs to be fixed? I guess I
could put
a preference in to disable auto-clicking of the close button on popups...
Original comment by steven.h...@gmail.com
on 18 Jan 2010 at 9:17
I'm not playing play-money SNGs, I play 16+ real money SNG tables, and the
problem happens when I use
[Apple]+W to close a completed table, and just before that another table pops
up. The still active table is then
closed by blazingstars. It can be a real trouble to find the closed but still
active table in a list of 16 tables, while
playing another 15. I can live without a fix, now I click the close button
instead of using a hotkey, but it requires
me to switch from keyboard only to using the mouse.
P.S. typing this I realize how lazy I am, switching to the mouse, the horror!
Original comment by derk.b...@gmail.com
on 19 Jan 2010 at 7:42
Uh, sorry, I meant that since I only play cash games, the fact that PS has SNGs
that
I can buy into with play money means that I can test tournament features a
little
more easily.
So, wait, I'm not sure I understand. You press Command (Apple)-W to close a
table, a
second table pops to the foreground, and then BlazingStars closes the table
that has
just popped into the foreground? Have you mapped Cmd-W to the "Leave Table"
hotkey?
I don't understand how BlazingStars is responsible for closing the table, the way
you say it. It sounds like OS X is closing the window because you asked it to
with
Cmd-W... I must be missing something. Has anyone else seen this?
Original comment by steven.h...@gmail.com
on 19 Jan 2010 at 10:03
Here's a comment from Andrew, sent by email because he can't comment right now:
I think I know what he's talking about. I've had this happen a few times and
it's
probabbly the same function that was taking care of the "checking is free"
window and
the "you've been moved to a new table" message.
Sometimes when I'm playing a lot of tables I'll accidentally click the "X" red
button
in the top left corer of of the table's window. Upon doing so, Stars initiates a
message of something like "Are you sure want to close this table, you are still
in
this tournament?" and BlazingStars will automatically click the "Ok" button
just as
it takes care of similar windows as mentioned above.
I'm pretty sure this is what he's talking about, but in his case he's trying to
close
out a table that he's intending to leave with his short cut command, but in
trying to
do so another active table pops up in which he doesn't want to leave getting the
command to close out. Without Blazing Stars on, he'd simply click cancel in
Star's
message mentioned above.
Regards, Andrew
Original comment by steven.h...@gmail.com
on 20 Jan 2010 at 5:40
Okay, it's a bit of a hack, but I think that I can solve this. Let me know if
it
breaks anything else; given that these things depend on the window titles,
it's hard
to keep track of all of the various titles so that I don't screw something up by
accident.
Original comment by steven.h...@gmail.com
on 27 Jan 2010 at 10:56
I've committed a change to handle this problem: a new preference has been added
to
allow the behaviour to be turned on or off. A new debug build is up with this
change
in it.
Original comment by steven.h...@gmail.com
on 27 Jan 2010 at 11:15
Closing this one off to work on other problems.
Original comment by steven.h...@gmail.com
on 28 Jan 2010 at 5:08
Original issue reported on code.google.com by
amar...@gmail.com
on 15 Jan 2010 at 7:09