Re: [pyAlarm-users] OS X Work
Status: Alpha
Brought to you by:
davidfancella
From: Dave F. <da...@da...> - 2006-09-22 06:20:50
|
On Thursday 21 September 2006 8:17 pm, Nick Allgood wrote: > Just thought id let yall know im still working on it and still want to be > apart of this project. Just relax. :) This isn't a job or anything, it's a free time sort of thing, so whatever you're willing to give is what we're happy to take. I did want to comment that I'm finding the pyQt3 rewrite to be a lot better than the old wxPython versions. I run two alarms per day, one at 6:30am for my wife to get the kids to school, and then a later one for me to get to school. Since I added the ability for the mixer to grab the sound card levels, then max the whole thing out, then restore the old sound card levels, she's no longer just turning off the speakers. She's actually hitting the stop button, which means it's already setup for the next alarm. I actually have a total of 4 alarms set, 3 of which run on different days because I wake up at different times on those days. Added bonus, if she's surfing the web while I'm still sleeping and hits a stupid website that has sound effects, she's not accidentally blaring them (our computer speakers in there are pretty loud). I haven't run into stability issues yet. It did segfault randomly after running for about 4 days straight, but the segfault happened in the middle of the day after we were all already awake. So keep an eye out for that segfault. I'm going to add some more verbose logging (read: enable the debug logging facility) to hopefully track down that segfault, but it hasn't recurred, and I've run it for longer than 4 days since then. I also haven't examined the sleep log yet, but I have used it already to verify that the alarm went off one morning where I slept through it. That was nice to have. Even with the wxPython version I could never be sure that I slept through the alarm or that it didn't go off, so I could never be sure how stable it was. Dave > Regards, > > Plazma |