Occasionally someone asks us, “one of my HUD panels has gone, how do I get it back?” It is usually lingering far to the left or right, off-screen. To get it back, one needs to move the poker window to various places on the screen until the missing panel becomes visible. It is somewhat awkward to explain, so I’ve reintroduced a little known menu option that we removed earlier this year:
The Head-up Display menu now has a “Reset Head-up Display Panel Locations” menu item. Wordy but clear I think. Most of you will never have to use it, but if you do it will be helpful.
Sometimes automatic updates don’t go as smoothly as they should. Our auto-update process broke with Poker Copilot 4.00, 4.01, and 4.02. These updates are now crashing every time you start them up.
After the update, you’ll notice that some of your statistics are not showing fully in the HUD. Select from Poker Copilot’s menu, “File” -> “Reload Hand Histories” to rectify this.
There are two small but significant changes in this update to how Poker Copilot works internally: A new system for detecting new hand history files means that the HUD appears almost instantly on a new table after completing the first hand; and a new system for detecting poker room table windows we developed for SeeingStars and integrated into Poker Copilot means Poker Copilot no longer needs to “control your computer.”
Because these changes could have consequences that didn’t appear during testing, we’re not making this an “auto-update”. You’ll need to manually download this update.
What’s changed
In OS X Mavericks, Poker Copilot no longer needs permission to control your computer.
If you have an Omaha addon license, you no longer need to enable Omaha in the Preferences.
“Mucked Cards” HUD overlay presentation is improved.
After playing your first hand at a new table, the HUD should appear almost instantly.
Today, I took a look at Lock Poker’s brand new native Mac software. It is rather good. And it should be possible to integrate it with Poker Copilot. However there are very few players, so it makes me wonder whether it is worth spending the time adding support for Lock Poker to Poker Copilot.
If you use Lock Poker on the Mac, let us know at support@pokercopilot.com that you’d like to see Poker Copilot work with Lock.
It is nice software, response, quite elegant, and it feels like Mac software. Oddly, the playing cards let it down – they are squashed, and awkward to read. Hopefully that’ll be fixed soon.
I hope not. But if you did, it is Poker Copilot’s cutesy way of presenting a crash report. Expand the “Details” panel and you’ll see some incomprehensible gobbledygook:
Those details are almost as incomprehensible to programmers as they are to you. At first. But as programmers spend time supporting software, they get better at analysing the crash reports. Over time they can use it to pinpoint some problems they didn’t know could exist.
Here’s what I do with Poker Copilot crash reports when I receive them.
Is this for the latest Poker Copilot update? If not, discard it, as the problem might now be fixed, and recent changes to code will make the crash report hard to use.
So it is for the current update? Use it to find the problem immediately, on the day the report was received. Fix the problem. Add the fix to the next Poker Copilot update.
Over time this makes a product more and more solid. At first the issues are common problems. Over time the problems that are left become esoteric problems that might affect one person a month.
Please do send crash reports when they happen. They do get to me. I do use them. In fact, I use them religiously because let’s face it, we want our software to be as solid as possible.
