Quote:
Originally Posted by fnord_too
Suggestion for the HUD (if you are not already doing it this way, and it does not look like you currently are):
Make the configuration file variable, so one can save multiple configurations (and load from same). Also, I am not sure how you are distinguishing between table types (HU, 6max, 8max, 9max and 10max), but that may be an issue. If you take the suggestion you can just select a configuration (assuming you are not playing multiple table types at once) or you can autodetect and load the selected default for that table (or if you wanted to get really fancy, the selected default for table type and game).
I don't think adding this flexibility should be very hard, since it looks like you are already loading from an XML file, and adding a lookup table for table size and or game type (or just a default selection dialog) should be pretty simple. However, there is a lack of this simple functionality in every HUD out there except Poker Observer, afaik.
I am happy to discuss the config file right now because I am getting ready to break it to add more configuration options. Then I want to freeze it so that I can do a nice configuration option screen.
I have tried to allow a reasonable amount of configurability, without getting it all too complicated.
Here is a layout paragraph from the config file:
Code:
<layout fav_seat="0" height="546" max="6" width="792">
<location seat="1" x="681" y="119"> </location>
<location seat="2" x="681" y="301"> </location>
<location seat="3" x="487" y="369"> </location>
<location seat="4" x="226" y="369"> </location>
<location seat="5" x="0" y="301"> </location>
<location seat="6" x="0" y="119"> </location>
</layout>
That is the layout for 6 max tables on PokerStars. There is also layout info for 8, 9, and 10 max tables. There will be similar paragraphs for other poker sites. N.B., the fav_seat, height, and width elements are not used for anything in the current version. I plan to use them later to support favorite seats and resized windows.
Here is what the paragraph looks like that defines the stats:
Code:
<game cols="3" db="fpdb" game_name="omahahilo" rows="2">
<stat click="tog_decorate" col="0" popup="default" row="0" stat_name="vpip" tip="tip1"> </stat>
<stat click="tog_decorate" col="1" popup="default" row="0" stat_name="pfr" tip="tip1"> </stat>
<stat click="tog_decorate" col="2" popup="default" row="0" stat_name="ffreq_1" tip="tip1"> </stat>
<stat click="tog_decorate" col="0" popup="default" row="1" stat_name="n" tip="tip1"> </stat>
<stat click="tog_decorate" col="1" popup="default" row="1" stat_name="wtsd" tip="tip1"> </stat>
<stat click="tog_decorate" col="2" popup="default" row="1" stat_name="wmsd" tip="tip1"> </stat>
</game>
As before there are similar paragraphs for the other games--you can use different stats and different popups for different games. The click and tip elements are not currently used. I have also wired around the db element for now.
So as currently programmed the HUD determines how many seats are at your table and selects the layout for that table. It also detects the game you are playing and adjusts the stats and popups accordingly. If you wanted to have 2 sets of stats and use one for 6-max and one for full ring, that is not supported in the current code.
So I think what you are suggesting is to create stat configurations with arbitrary names that could be easily changed. This is basically what I have done with the popups, you can defind as many of those as you want and tie them to different stats. I have thought about this some in the last few days without actually deciding if that is something I want to work on. But
I am happy to have feedback on this design choice.