freepokerdb

On Thu, Jun 17, 2010 at 4:45 PM, gimick <bbtgaf@...> wrote:
> I'm taking a quick look at this.
>
> Releasing with this issue is going to generate a lot of complaints I feel -
> it locks up your poker client at the very point where you must bet or call
> to win a big pot.
>
> One immediate workaround is to disable the window close button for that
> window.
>
> I offer the following changes at line 101 of HUD_main.pyw (SQL coder GIT):
>
>  self.main_window.set_deletable(False)
>  self.label = gtk.Label(' To close, use "Stop Autoimport" in FPDB.')
>
> Immediate testing seems succesful in the windows source code version.
>
> two immedate questions:
> Any reason not to disable window close button temporarily?
> SQL coder, could you build an exe to see if this works OK?
>
> I'll carry on testing this hack a bit more, and also trying to understand
> why it locks the other windows.  I'll need to setup a py2exe environment, so
> it isn't going to happen quicky.
>
>
> Steve~
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> Fpdb-main mailing list
> Fpdb-main@...
> https://lists.sourceforge.net/lists/listinfo/fpdb-main
>
>

Pressing Stop Autoimport also gives me several seconds of nearly total
freeze before it stops, too.


-- 
Eric Blade - 707-99-BLADE
http://www.landofthedeadmatchmaking.com/
http://finder.game-server.cc/
http://ericblade.postalboard.com/

>
>
> Pressing Stop Autoimport also gives me several seconds of nearly total
> freeze before it stops, too.
>
>
>
Thanks for the confirmation that you have the same issue Eric, much
appreciated.  The suggested hack seems ok on winNT source code install, and
I'm just testing on Linux, to make sure there are no other apparent
problems.

quickly tested on Linux/Gnome and seems to work OK for me.

I've pushed a patch to my git
***6189a67b1e<http://www.assembla.com/code/fpdb-gimick/git/changesets/6189a67b1e091eb1b8487498e56b68dddc5cf2dd>
* git://git.assembla.com/fpdb-gimick.git

Sorrow, my GIT is sync'd from you, but this patch needs to be merged with
SQLCoder's latest changes.  If you run this patch against your git version,
you will hit a problem where the HUD_Main window does not close when "Stop
Autoimport" is pressed.  SQLcoder has fixed this in his GIT.

Also I could code this to be a NT only change, but felt it was cleaner in
the code to have the same temporary hack for all OS's.  Non-windows users
will not have a close button in the HUD window - don't know if that is
acceptable?

>
>
> Pressing Stop Autoimport also gives me several seconds of nearly total
> freeze before it stops, too.
>
>
> sorry Eric, I totally mis-read your comment - Stop Autoimport for me is
immediate.  Does the same delay happen with no poker client running?

On Thu, Jun 17, 2010 at 6:59 PM, gimick <bbtgaf@...> wrote:
>
>>
>>
>> Pressing Stop Autoimport also gives me several seconds of nearly total
>> freeze before it stops, too.
>>
>>
> sorry Eric, I totally mis-read your comment - Stop Autoimport for me is
> immediate.  Does the same delay happen with no poker client running?
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> Fpdb-main mailing list
> Fpdb-main@...
> https://lists.sourceforge.net/lists/listinfo/fpdb-main
>
>

Hmm. I just tried it right now, and I got a message box saying that I
needed to look at the hud_main.exe.log file.  All the poker windows
that it was attached to were closed at the time, and I don't know when
these errors actually occured:

It tells me:

hud         : ERROR    self.window doesn't exist? why?
hud         : ERROR    Table "Portland XV" no longer exists

The entire program was halted while awaiting a response to that
message box - and the message box appeared UNDER all other windows.
(have I ever told anyone about how much I hate GTK's focus issues?)

 (get the same issue if you try to play with other tasks while you
have some prompt from the Configuration windows up, you can lose the
configuration prompt behind the FPDB window, and the only way to get
around it is to kill fpdb)

After pressing OK on the message box, it was maybe about 2 seconds
before the HUD_main window closed, and it returned control to me.

Pressing Start then Stop right after it starts has no delay.. i'm
trying to see what happens if i import a couple hands, and close it
while the table is still up, and then try after a couple hands,
closing the table, too.

No problems there, either.

It seems like my problem might be related to this popup-box here --
the error message in the log occasionally occurs, when we process a
new HH after the table window has already been closed. So, it might be
freezing because it's waiting for me to acknowledge these error logs,
even though the errors occured hours ago.




-- 
Eric Blade - 707-99-BLADE
http://www.landofthedeadmatchmaking.com/
http://finder.game-server.cc/
http://ericblade.postalboard.com/

On Wed, Jun 16, 2010 at 5:52 PM, Eric Blade <blade.eric@...> wrote:
> You can list me as "Eric Blade" not "Ekdikeo" if you'd like (one or
> the other, not both please :) )

I've changed that to 'Eric Blade' in the notes, and in the 'About'
box. I changed my own name while I was at it.

Anyone else have a preference for what name they are listed as?

> I'm noting that the "Session" viewer apparently includes tournament
> hands in it's calculations, I expect that should be an easy fix.

Eek - theres 4 queries - 2 for mysql, and 1 each for postgres and sqlite.

I think i've fixed that now.

Carl G

On Thu, Jun 17, 2010 at 1:00 AM, Steffen Schaumburg
<steffen@...> wrote:
> Sounds good. I just tried 20100614 in XP Pro SP3 x86 and it works great.
> I also tried it in Windows 7 Home Basic amd64 and it works fine, except
> the HUD doesn't work if I use run_fpdb.bat. HUD works fine if I right
> click > run as admin on pyfpdb\fpdb.exe though. I'm not sure but maybe
> it's possible to change the .bat to automatically run fpdb.exe as admin?

Known Issues:

"Windows 7 and Windows Vista require that fpdb.pyw be 'Run as Admin' -
the HUD will not run using the run_fpdb.bat startup script."

> I'd reword this a bit, in particular it sounds like we actually do
> import from any site. How about this: The import engine has been mostly
> re-written in this period, and now has a solid structure that can easily
> be used to implement support for any site that writes a hand history
> file to the local disk.

Went with
- Much faster and more flexible HH importer. The import engine has
been replaced in this period. FPDB now imports hands more than 400%
faster than the 0.11 release. It was also built with a solid structure
that can easily extended to support any site that writes a hand
history file to the local disk.


Carl G