HUD has dependency on auto-importing

[adamg]

Why can't I use the HUD while I'm not auto-importing? It seems that the "Start HUD" button is disabled unless one is importing. This doesn't make sense to me. Sure, it's true that usually you're going to be importing when using the HUD, but the two tasks are in no way dependent on each other.

[Josh]

How often are you going to want the Hud without the hands being imported? I can't see any reason why you wouldn't want the stats updating.

[alonalbert]

I think it's just a presentation issue. The start HUD button should enabled regardless of the auto-import but should start the auto-import when clicked.

[Sreip]

How often are you going to want the Hud without the hands being imported? I can't see any reason why you wouldn't want the stats updating.

When you are importing the hands on another PC, probably to reduce CPU overhead on the computer you are playing.

[Pilli]

How often are you going to want the Hud without the hands being imported? I can't see any reason why you wouldn't want the stats updating.

Another reason why this may be usefull:
You could use the HUD for table selection on sites that don't allow observed hands imported. You could quickly preview the players on a table by enabling the HUD and having a peek.

[adamg]

How often are you going to want the Hud without the hands being imported? I can't see any reason why you wouldn't want the stats updating.

I guess the use case is fairly limited. I ran into it when I wanted to test out the new HUD and couldn't because I wasn't playing at the time (I enabled Auto Import, but the HUD didn't appear to be working since I wasn't importing any hands).

I guess the fact that no one else has complained about this is probably a sign that it's an OK design, but I just don't see what harm it would do to have that button enabled and and still start (if stopped and "Start Automatically" is checked) when one beings Auto Import.

[Josh]

The auto-import routine was designed to use as little CPU as possible. On my computer, with just auto-import running, my CPU regularly stays at 0 CPU usage.

For sites that have auto-import capability, but don't directly support observed hand histories (like Stars and Party), PT3 will have a method that works alongside auto-import to obtain the player information.

The Hud relies on information the auto-import process gathers in order to function, so the auto-import will continue to be necessary.

[Sreip]

The auto-import routine was designed to use as little CPU as possible. On my computer, with just auto-import running, my CPU regularly stays at 0 CPU usage.

FLW. How many tables are you importing, 100+?

Actually, you cannot have two PT3 instances importing into the same database at the same time. This WILL cause problems.

Would it be possible to run the import in ‘read only mode’. So you do not update the database, just activate the HUD.

[Josh]

I've had auto-import importing from 12-16 tables before with very little CPU usage.

I suppose it would be possible to have the auto-import running without actually importing, but only if it's something that will be used by a good number of users.

[Sreip]

How about if you could import into a different database to that which you are getting the HUD data from? E.g use observed hand history database for HUD while importing into personal database? (Although I still think a read-only option is best.)

By the way what goes wrong if you import into the same database from two computers. I have been doing this for the last fortnight and not noticed anything. PostgreSQL ought to be able to handle multiple access. Perhaps this could be fixed instead?