NOTICE: This forum is mostly an archive, though new posts are allowed. Registration may require manual admin activation. After registering visit https://bitsum.com/contact/ to request account activation.
Started by Jeremy Collake, June 08, 2012, 03:10:54 AM
Quote from: bitsum.support on June 12, 2012, 12:53:51 PMAt this time to keep track of changes would be another slow down, as there are a gazillion each build. They will start when I hit beta. I will try to note large functional improvements or changes though.
Quote from: bitsum.support on June 12, 2012, 05:18:04 AMv126.96.36.199 ALPHA issued
Quote from: bitsum.support link=topic=1452.msg6800#msg6800 date=1339776354Once we get to beta, then start flooding with issues ;)/quote]Roger that!
Quote from: hanemach_gt on June 16, 2012, 03:23:53 PMEnergy Saver exclusions are wanted by me, big plus to you for extending this wonderful feature.
Quote from: bitsum.support on June 18, 2012, 03:06:15 PMSomething many wanted ...
Quote from: edkiefer on June 18, 2012, 05:36:37 PMWhat was the old "periodically check for updates " frequency rate ?
Quote from: bitsum.support on June 18, 2012, 04:51:00 AMThere is still a known crash in 2K/XP in the Active Processes Tab. I haven't got to even look at it yet, but will make it my next priority.
Quote from: bitsum.support on June 18, 2012, 05:49:16 PMTwo days. The alpha is accelerated in its frequency though.
Quote from: edkiefer on June 18, 2012, 06:26:48 PMOk , The per core overlay graph been fixed in last 2 builds and seems I wasn't affected by XP active process crash , maybe because i didn't have enough processes running .
Quote from: Tarnak on June 18, 2012, 06:25:57 PMJust tried v188.8.131.52, and it is fixed for me!
Quote from: Tarnak on June 18, 2012, 06:54:52 PM[.46]Addition.GUI: Clicking the graph will rotate through available application color schemes (currently only white and black) See - The above change introduced in V184.108.40.206 is not functioning in v220.127.116.11 with XP.
Quote from: bitsum.support on June 18, 2012, 07:11:16 PMYea, I know, thanks though. I disabled it. It will be fixed up. The rotation didn't work well with the new components yet.
Quote from: Tarnak on June 18, 2012, 07:16:18 PMAt the moment I get the new 'Core graph', blinking in and out.
Quote from: bitsum.support on June 19, 2012, 08:27:58 PMNote you do have to click the actual graph now to change themes. In v5, any extraneous click could change themes, something that was both good and bad. I left it as an easy way to accidentally introduce the user to these types of theme changes, but v6 locks it down to the graph region only.
Quote from: bitsum.support on June 23, 2012, 02:08:40 PMHe is speaking about self-restart on an interval, which restarts the GUI and governor every X hours. That code is a bit separate, though does share some code paths, but is likely malfunctioning.
Quote from: edkiefer on June 23, 2012, 02:38:07 PMOk, I see now, I missed that option (self restart PL interval ). I have to ask though why would you ever need to restart the GUI , I can see processgovernor having some kind of issue but not GUI .
Quote from: bitsum.support on June 23, 2012, 02:57:32 PMOh, and I also have a BIG new document introducing all the internal features of Process Lasso v6 ... It is an important upgrade to the docs anyway. It is not done yet, not by a long shot, but I will start publicizing parts of it as I complete it. Feature by feature.I've added a lot of new sanity checking in v18.104.22.168 (yet to be released) to help track down remaining aberrations, which I haven't spent much time on yet as I focus on features and functionality.
Quote from: bitsum.support on June 23, 2012, 02:54:00 PMIndeed, there is no good reason. I put it there as a safety, in case someone, in some distant universe, had an issue where a third-party DLL injected into Process Lasso was leaking memory or handles. Of course, with newer self-integrity checks this is even less important, as Process Lasso monitors itself to make sure nothing looks out of whack. If it does seem out of whack, it will restart with a message. Nobody has seen this occur I'm sure, except me while testing the mechanism.