please add an option to remove all money-related values from the session window.

i want to see the number of hands i played, but not if i'm up or down. i play a lot worse when i'm down.

Yea, tabbing is a bit all over the place atm - will get that fixed.


In the next version (probably) you'll be able to pick and choose what you want to see independently of what you're checking against.

I'm wondering if it's possible to NOT have the session info reset if you happen to close the program. I've done this a couple of times, and even though I had remained playing at the poker site, VC cleared the session data, thus resetting the limits & alerts. If it's checking your db (in my case it's HEM) couldn't it just use that info for your current session?

Also, this is a BIG request for me: a SNOOZE button, or something like it. Right now, if I hit the a limit which triggers an alert, the warning message will keep going every few seconds. Often this happens when I'm still involved in a hand or two, and sometimes they are important hands that I want to finish out & concentrate. If I'm being reminded that I just dropped below my stop loss amount, this tilts me for the hands I'm still involved in. Is there a way to stop this w/out closing VC completely?

I don't want to tie it to a HM/PT3 session, but it should be fairly simple to give the option of using a start point until it's manually reset.

Ticking the 'alert just once' checkbox on the setup-screen will give the warning just once. You can also tick/untick this checkbox while the check is running, toggling the repeated alert on/off without resetting the session.

for me, the session window minimizes to system tray along with the main window despite only checking the box for main window minimize

Yes, I've noticed the minimize-functionality can be kinda wonky - the two windows aren't functioning quite as independently of each other as they should.

I'll have a look at it.

That would definitely be nice if it's not going to be tied to the database's info.

Yeah, but I guess the problem is that if I trigger an alert and am still involved in a few hands, clicking the "Alert Just Once" basically turns off the alert from then on, correct? Also, there are times when, for example, I get sucked out in a really huge pot which, let's say, puts be just under the #bb I set up ... but I'm also positive I'm playing at a super soft table (or several other soft tables) so stopping altogether would be -EV. It would be cool to just hit a snooze button once & forget about it which would allow me to hang in there for another few minutes to reevaluate whether some fish just caught a one-outer in a monster pot, or if I'm really playing poorly, tilting, getting out played in general, etc.

I guess I just like the option for there being a gray area, and it seems like a snooze button would allow for that. (Hope that makes sense.)

New version is up: http://home.haugnett.no/minusev/ValueCheck.zip

Some changes to the Setup window:



What values to show in the Session Window can now be selected independently of what values are being checked against, by choosing these in the 'Show in Session Window' section.

Also, tabbing should make a bit more sense (though I just noticed it skips the 'Session high point' checkbox...).

I'll try to get this into the next version.

It makes sense and I like the idea - will have a look at that for the next version.

I think the best way to do it is to add a snooze-button to the session window and options for whether or not it should show, and if so, how long the snooze time should be.

I'd like some input on how people think it should work though - should hitting the snooze-button cancel all alerts for the time it lasts, or just the ones already triggered?

If you hit the snooze button because your bb lost target is reached, but then your target for number of hands reached triggers while the snooze is active, I'm thinking this should still trigger an alert, or should it wait until the snooze-time has expired?

I'd say that since you're mostly getting alerted about one specific thing (let's say minutes played as opposed to bb's lost) the snooze should just be for that one alert. So if you reach X minutes and you're feeling ok & don't want to take a break until the orbit is complete and your back in the big blinds, the snooze would handle just that issue.

But let's say in the few minutes between the time that you reach the time alert, you also suffer a bad beat losing a huge pot which puts you below the limit for bb's lost, this deserves another (separate) alert. Basically, the first alert is there to remind you to get off your butt, stretch your legs, etc., while the second reminds you that you might be on a serious tilt because of that last hand you played. For the same reason that you can opt to have different sounds alert you of differnt scenarios, the snooze should be situation-specific, imo.

Cool! ... but what's not cool is that you have to reset your config info every time you update the software. Not a huuuuge deal, but it would be nice if VC could keep your basic config setting saved separately so you don't have to re-enter everything. Thanks!

Played Hands is not working using PT3, Session windows shows 0 hands played after playing some hands

Have you changed your db to PT3 and selected your sn on the configuration screen after updating? All settings are lost after updating to a new version (which is a bit of a pain and I'll see if I can't change this soon), so you have to set that up again.

It seems to work on my machine at least.

Yes I did that, for example the $ won/lost is working fine as the minutes played.

Did you uncheck and check the 'show hands' while the check was running? That may stop the updating in the Session Window.

If not, could you try if it still notifies you when the hand goal is reached (just set it to 1 or 2 hands) so it's just the update of the session window display that's not working?

software not working for me. i use pt3. when i try enter my name it freezes up a i try type name.then a box comes up saying database not found.
anyone got any idea?

Have you selected PT3 as your database in the configuration screen? And then made sure the database details matches your setup (name, password etc?)

You also have to click the 'save' button after updating these details.

The first access against a PT3 database does take a while and the program appears to be frozen while waiting for it to return, but it will update after a little while.

Not sure why this is tbh, it doesn't happen when I run it against HM - but it only affects the initial selection of the player so it shouldn't have any impact on using the program once this is in place.

It's working now lol I have no idea why it wasn't working yesterday.

Great

yes it still wont load names for me. im 99% sure my details are correct as ive seen them somewhere before. where would i find these details and is there any other reason why its freezing and getting an error display?

You can find the database details (except the password) by going to 'database' and 'database management' in PT3. The name, server, port and username will be under the 'database info' header.

If it freezes, it sounds like your database is set up correctly though - otherwise it wouldn't have a database to check for long enough to freeze.

What computer specs and OS are you running it on?

It would also be helpful if you could give the exact error message you're getting.

Never mind about this - I know what's causing the slowdown for PT3 and will have a workaround ready soonish.

I'll probably have to stop showing the number of hands in the player selection screen for PT3, but this isn't of much value anyway.

Hopefully this should solve ricky19745s issue as I suspect it's caused by the access timing out.

there is a problem with connecting to the database. i know all my details but this version wont work

New version is out: http://home.haugnett.no/minusev/ValueCheck.zip

Only change in this one is the mentioned fix for the freeze when selecting a player from a PT3 database, so unless you have problems with this, there's no need to download it.

If it's worked previously, I don't see any reason why that version shouldn't also - there were no changes made to how it connects to or reads from the databases. Are you sure you've updated your database details (and pressed 'save') after installing the new version?

If you use PT3, please download the new version and see if that fixes it. If not, please give some more details about where it fails, whether you use it with HM or PT3 and the exact error message you get.