Heads Up display doesn't wake up after sleep in 2.08
Normally in the weekend I open both FullTilt Poker and Poker Copilot and don't close them again. Instead I close mu laptop and that puts the computer to sleep. When I open again FTP.app reconnects and until 2.08 PCP just worked.
But after updating to version 2.08 PCP's head up display doesn't show. Main window does work. I have to restart PCP before HUD works again
But after updating to version 2.08 PCP's head up display doesn't show. Main window does work. I have to restart PCP before HUD works again
2
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
-
Inappropriate?I'll investigate this.
Regards,
Steve
---------------------------------------------------
Steve McLeod
Founder, Poker Copilot
http://www.pokercopilot.com -
Inappropriate?I found these messages logged to Console:
2009-09-25 21:43:30 WindowMoveDetector[39336] Sending messages to port 51310 every 0.50 seconds
2009-09-26 9:44:45 WindowMoveDetector[39336] in onSocket: willDisconnectWithError:
2009-09-26 9:44:47 WindowMoveDetector[39336] err = Error Domain=NSPOSIXErrorDomain Code=57 "The operation couldn’t be completed. Socket is not connected"
2009-09-26 9:58:42 WindowMoveDetector[40951] Sending messages to port 53645 every 0.50 seconds
I’m confident
-
Inappropriate?This is fixed in 2.17.
There are still error messages logged to console
I’m happily surprised
-
Inappropriate?I was hoping you guys would notice this in 2.17!
Regards,
Steve
---------------------------------------------------
Steve McLeod
Founder, Poker Copilot
http://www.pokercopilot.com -
Inappropriate?Steve, today I noticed that my Macbook Pro 13" was much warmer than normal and that the battery was draining more quickly than usual. I looked at the Activity Monitor and noticed that the WindowMoveDetector process was consuming 85% of the CPU.
When I stopped Poker co-pilot the WindowMoveDetector process did not stop and I had to manually kill it. I restarted co-pilot and it has behaved normally.
Not sure if I did something to make the process spin. I had been running co-pilot continuously for about 4 days w/o rebooting the mac (I frequently sleep and wake my mac).
Otherwise no problems and very happy with co-pilot. -
Inappropriate?Hi Randy,
Thanks for reporting this.
You should update to Poker Copilot 2.20 (the current release) which no longer requires the separate WindowMoveDetector process. It also uses less CPU.
Regards,
Steve
---------------------------------------------------
Steve McLeod
Founder, Poker Copilot
http://www.pokercopilot.com
Loading Profile...



EMPLOYEE
