This is fantastic news. I have downloaded this version and will report on any problems, or with further suggestions if I have them.

eleatic: i've been waiting for you to pop in and check this out I've found that minimizing the windows does not make the huds go away properly (future changes planned to make this work, im just researching if i have to write it myself, or if i can set something somewhere that will cause windows/an x window manager to deal with it for me) .. but as long as you aren't the type that minimizes every window that you're not immediatly looking at, it should work out right.

I have run 3 and 4 tables with it, with very few problems, on a site that isn't technically "supported"

I’m not surprised to hear it works with “unsupported” sites; in its current state the HUD seems very robust.

I’ve had a chance to try the HUD out to the tune of a few hundred hands with my standard arrangement of eight stacked tables (though I usually play on more than eight). It ran entirely without (significant) fault. More testing to follow. Everything is as advertised. This is a real quantum leap in the quality of the user-interface. Well done!

I have come across three slightly strange bugs, though extremely trivial ones. Firstly, some of the tables seemed not to get their HUD straight after the first hand had been played, but after a few hands. Perhaps a new HUD appears only if the table is currently visible? Secondly, while the HUD is running (I think) and after it has been closed the Fpdb main window stops responding. When I then press ctrl-C in the terminal window (in which the error messages appear), the automatic importing stops and the main window wakes up again. Since at this point I just want to quit, this doesn’t matter. Thirdly, for some reason the statistics window for seat 9 (nine-handed on Poker Stars) is sometimes, but not always, slightly out of position (about 20 pixels to the left of where it should be).

I didn’t try to minimize any of the windows while playing as this seems pointless, so I would tend to regard this “bug” as trivial as well.

Once again, my congratulations to the developers!

This is good news. The hud windows should appear after 2 hands. I haven't tracked it down yet, but it is consistent.

With the 20 pixels measurement, what corner is out? top left? the windows resize to compensate for stats - i haven't looked at how that is done yet.

Haven't seen the hud main window hang yet, i'll keep an eye out, i'm sure Ray will read this soon.

This is actually happening in the importer. It seems to be noticing the new hh file and putting it on the list of files to watch, but doesn't actually import from it until the 2nd hand goes in. I think this is something we can fix. pytgtk programs do not respond correctly to ctrl-Cs. They have a hack in their FAQ that makes ctrl-Cs work, but it uses a lot of cpu to watch for that signal--meaning we probably don't want to use it. Closing the fpdb window exits more gracefully. This is weird. I have not seen that, so I'll play some holdem and see if I can replicate it.

The whole window appears slightly to the left of where it should (and of where it actually does appear on most of the tables – the fault occurs only sporadically). I didn’t actually count the pixels. My theory is that this is an artifact of unwanted interaction between different threads (trying to display the window and update the statistics at the same time); I came across something similar when I hacked the earlier version.

If it’s consistently two hands I wouldn’t bother to “fix” it. It’s not a bug; it’s a feature.

Strange; I’ve always found them to respond correctly, except perhaps in this case. As I said, you hit ctrl-C, and like magic the main window starts responding again.

I’ve had another try – about 400 hands. The HUD stayed operational during the session, but some minor bugs showed up.

The problem of the “misplaced” stat window is a bit worse than I thought. Sometimes they all get misplaced. They appear right on top of the window that says “right click to close HUD” and on top of one another and have to be positioned manually. This only happens on some of the tables. I will make efforts to find out what is going wrong.

The pop-up windows don’t work correctly with the HUD’s new appearing-and-disappearing behaviour. If you are unlucky and happen to open one a moment before a new poker table jumps to the front of the queue, you can’t close it any more. It stays there hovering over what is now the wrong table and won’t go away.

That said, once these difficulties are ironed out I think the HUD will be a must-have piece of software.

There have already been 2 changes comitted to fix this. I haven't tested them. Sorry, you're right, I misread the FAQ. This indicates that all the statwindows are opening at (0,0) relative to the poker client window. It seems the the HUD code is not getting the layout from the config properly. This one we can fix.

I've seen this a couple of times now since preferred seat came in (or possibly a little after), seat 6 (on 6 max) will be created somewhere nowhere near the window. I've had it appear at the bottom of the screen on occasion. No preferred seat was set though.

Its been ok for me for the last week or so fwiw, and i always saved the changes back to the config when it happened.

Eleatic: You are able to move the windows around? And you're using Windows?

So this means that somehow the fact that I can't is a bug local to something on my computer. Ugh!


I just pushed a fix to the popups, so they should attach to the window they came from now, and start with the correct color selection (excluding opacity, having a bunch of partially opaque windows on top of each other looks awful)

No: Linux. If you can’t move them this must be Windows-specific.

I haven’t played today so I can’t comment further on the problem, but still feel it is a bit more complex than has been suggested, since it is intermittent. All my tables are the same (I stack them), yet the problem occurs only on some of them and not on others.

I have spent some time staring at the HUD code and don't see why the stat windows are not locating correctly. Do you use the preferred seat feature? Do you think this happens 1% of the time 10%, 50%?? If I don't think of something in the next couple of hours, I will fix up a version with lots of intermediate prints and ask you to run that.

I pushed Eric's fix to the popup just now. So you probably want to get the most recent from my repo.

Eratosthenes: I’ve already added code to print out the values being used, and they are all correct; but the problem is still ocurring. I would estimate it happens about 10% of the time, but it is unpredictable. I don’t use and have never used the preferred seat option.

I have now tried the HUD again after adding this function

to the right-click menu of the HUDs, and it puts all the windows back to where they should be – which only adds to the mystery. As you can see, the x and y values are being set correctly, but then the windows, or some of them, are displaced for one reason or another.

I am still of the view that something is going wrong with the thread-locking, since I came across similar graphical artifacts caused by this in the earlier hacked version.

If I can’t crack this myself I will upload a screenshot.

And if you are having trouble re-creating the problem, try sitting down at 20 full-ring play money tables, or failing that 20 full-ring 1c–2c tables, on PS and see if it happens.

Patch please - ekdikeo wants to make the hud windows move with the table when you reposition, this is a good first step.

I’d be delighted; but could you please give me the exact Git command – I am too lazy to look it up.... And are you sure you really want the patch? By rights the function I’ve added shouldn’t do anything at all, and it wouldn’t were this error not occurring.

If you've been using git to pull the updates, then 'git diff' should show any uncommited local mods.

# git diff > patchname.diff

Should do the job.

The patch may not do anything now, but shouldn't take too long to mod to figure out where the new window position is.

Don't bother sending a patch. I just copy/pasted from the above and added the appropriate menu item to the popup menu.

I also decided to add an ugly kludge to see if I could avoid the problem. While adding said kludge, I found a pretty subtle typo that might have been the root cause!! So I have added both the fix to the typo and the kludge .

Steffen is putting together a release that will fix the change to the Stars HHs mentioned elsewhere in the Software Forum. That should be available in a few hours and will include these fixes.

Pokerstars real money Badugi games are supposed to be in Monday's update. Where would you like the HHs sent, to try and add Badugi support? Once you have basic Badugi support I will be wanting to download and install your application.

I’ve noticed something else that is not quite right: when the HUD has been activated the Fpdb process goes into a busy loop and steals all my processor’s idle time, even when there are no hands for it to import. This should be quite easy to correct.

I think I know what is going on in that. I'll take a look.

You should grab my git repo. It has the window positioning fixes in it. It will be out as an alpha release tomorrow to support the modified Stars hh format.

Hi everyone,
This is alpha9. Many changes have been made, virtually all of them by Ray, Eric and Carl, many of them in the HUD. There's also been quite a lot of work to clean up old code making it more flexible - this will pay off in the future because it makes things more maintainable and flexible. This version also supports PokerStars' new format which is being released on Monday.

Note that default.conf is no longer used, instead all configs are now made in HUD_config.xml (this includes options for fpdb's importer). Re-creating the database is not strictly required this time, but I'm not sure if people fixed potential importer bugs so it might be best to re-import anyways (in the main window select the Database menu and click re-create tables, then bulk import all your files again).

For a detailed changelog please visit the fpdb git tree at assembla.

For any bug reports or problems please visit our help forum at https://****************/forum/forum.php?forum_id=819272

Enjoy!

PS: I didn't have time recently to read this thread, the forums or mailing list, but others have been doing that. I'll catch up this week.

Here are a few of the improvements users will probably notice, besides the stars hh update:

• Good support for stacked/cascaded tables.
• Misplaced windows noted a few posts back should be fixed.
• Configuration parameters in default.conf will be moved to HUD_config.xml automatically. After that default.conf will no longer be used.
• Reasonable defaults will be used for most missing configuration parameters. For example, it should automatically find your Stars and FTP hand history folders.
• HUD colors are configurable --but you have to edit the xml file .
• The HUD will appear after the first hand played at the table, instead of the 2nd.
• Preferred seat support at Stars.
• Numerous bug fixes.
• Lots of good infrastructure improvement that are invisible to users for now, but will increase stability and allow more features later.
• Other things that have slipped my mind.

I’ve tried the latest version (the version in the Git repository, which I assume is the same as the version referred to by Steffen) and it works very well. The problem of excess CPU consumption has been resolved; I was going to try dealing with this myself, but there is obviously no need now. The statistics windows are still occasionally being misplaced, however.

New users, please see the install instructions on the Wiki, e.g. for Windows: http://fpdb.wiki.****************/Install+in+Windows

I will be updating and wikifying most of the documentation today.

There are some good improvements in this new version. Stacked tables and even minimized tables work well and the task bar has been cleaned up. The default.conf parameters moved over to the HUD_config.xml without any problems.

The HUD includes a small window in the top left corner that says "Right click to close HUD for (table name)". This obscures one of the hole cards for seat #8 on 8-max stud, razz and hi/lo tables. Not a huge problem, but just so you know for the next version.

Do you mean the HUD_config.xml in the pyfpdb folder? What lines should I look for to edit?

Thanks again to all the developers!