Version 6 misc

[Jeremy Collake]

Option removed in 6.0.0.23, we'll see if there are any complaints.

[Jeremy Collake]

I really like this change. Seeing the graph theme flip on any UI click was(/is) rather annoying.
Is there also going to come a user setting that "locks" it to either the dark or light theme?
I prefer the dark theme over the light one. 

Still on v5.x here. Don't know If I should start using a alpha/beta build. 

I have backported to v5.1.0.98, which is coming shortly. Please let me know if you have any troubles.

As for a theme lock, I will add that if I get a chance.

[GTX2GvO]

I have backported to v5.1.0.98, which is coming shortly. Please let me know if you have any troubles.

As for a theme lock, I will add that if I get a chance.

Yay. now the theme only flips when clicking the graph itself. 
I'll patiently wait for the theme lock feature for if/when (eventually?  ) it comes. 

[Jeremy Collake]

I can throw it in a v6 build real fast, no problem . I don't want to add it to v5 though, as it is another string for the translators.

[GTX2GvO]

I can throw it in a v6 build real fast, no problem . I don't want to add it to v5 though, as it is another string for the translators.

Understood, accepted and I can wait. 

[DeadHead]

Crashes on startup on my system, Win 7 Pro 64 bit (swe).

[Jeremy Collake]

I added a couple extra safeties for potential localization issues and am uploading v6.0.0.25 ALPHA .. though then am SLOWING DOWN to do proper code analysis and debugging, as opposed to sending out builds haphazardly, trying to address individual crashes or concerns. We'll get to those when we get to the beta stage.

UPDATE: Other non-English users reported .25 resolved the crash you saw, but do note that the per-core metrics may not work correctly.

[Jeremy Collake]

Windows NT 6.0+ x32/x64 English users should be good, I've ran it for a long time.
Windows NT 5.x English or non-English users -- can't recommend it, GUI may crash at times.

Others are untested on this end.

I've got MUCH MORE code review, debugging, and handling of various types of potential errors to do ... things are so far from complete.

[Jeremy Collake]

Recap of this week's progress:

+ Per-core metrics not shown if there is an error, as there will be on some systems in the current build
+ Support 'processname:username' syntax (with wildcards) in ProBalance exclusions and Watchdog rules
+ New 'random' (manually typed) affinity setting for ProBalance or Watchdog rules will select 1/2 of available cores at random -- per a user request, not something most will want
+ Restructured build system and the way our applications are digitally signed
+ Watchdog rule dialog further cleaned up and more functional
+ Watchdog 'log' feature added
+ Several bugs fixed, improved code
+ Many localization adjustments, and updated translations

[Jeremy Collake]

This is QA week ... FINALLY you say . I can't express to you the amount of work I've done already on QA, from down up. Instead of investigating each bug, I've developed more robust code to show ME the errors. That way, by the time we hit BETA, I hope to have everything resolved.

Version 6 BETA is scheduled for the end of the week. This is a major milestone. Thank you for your patience. This will be the most stable build of Process Lasso ever released, there is no doubt about that.

[Victek]

Definitely looking forward to it, thanks!

[Jeremy Collake]

It will be here. I can't express to you how much QA I've done already. I mean, my goodness. Whew. It nearly broke my brain yesterday. This will be the most stable major version ever released though. Version 5, when it first went final, had a few real-world quirks I didn't detect until it went final - because I had rushed it. Now, although people may complain, I am taking the time to do proper QA before I even hit BETA. Then, I hope to hear about any real-world troubles.

I should note that almost all troubles are with the GUI, something coded from scratch without fancy libraries to make it look snazzy. The core engine itself is generally solid, though there have been cases of it crashing using some of the more rare features that I don't recommend. These I'm also investigating this week.

[Jeremy Collake]

I may move v6 to beta before the end of the week even, to start getting early feedback. I don't know how many are using the alpha, but it would be nice if a few are ;p. I am...

[edkiefer]

I have been using ver 6 since beginning and other than first alpha's the rest have been stable here on XP and I have not noticed any crashing or restarting with GUI .

[Jeremy Collake]

Thanks Ed, that is what I like to hear . I believe at this point the v6 alpha is more stable the the v5 stable build.

[Jeremy Collake]

BTW, I added the 'Lock theme' option ... though it is grayed out in the current build, it will be enabled soon.

[Jeremy Collake]

This board is now re-opened to guests, as v6 approaches public beta. Although I should wait until EVERY feature is complete for EVERYONE before going to BETA, I have made the decision to go to BETA sooner rather than later because:

1. More users will be exposed to it for more feedback.
2. So many additional features are supported.
3. It will get the translators pumped up, and word out.
4. The features that aren't supported for some non-English users will be enabled soon, whether before or after the first beta. Either way, it is all good.

Do remember, I have that one additional UI element to show . You guys know what it is. When it is revealed, v6 will really be 'the bomb' for me. From there, v6.1 is already planned.

[hanemach_gt]

Well, I am going to proof-check translation and send it to you ASAP.

[Jeremy Collake]

Thanks . Note that there probably WILL BE a few changes between now and final, BUT ... that is always the case. I will try not to change too much.

[Jeremy Collake]

Tinfoil Hat, a tester and translator, and team member here, noticed that Probalance exclusions were NOT working in recent ALPHAs. This is because of the new allowance of usernames. I have fixed this in .37 BETA.

For instance, you can now specify (but don't have to):

someprocess.exe:MyUserName
some*.exe:Myuser*

or just stay with:

someprocess.exe

This allow control of which users have their processes excluded from ProBalance restraint.

[Jeremy Collake]

One thing to be done in the NEXT Beta will be a redesign of what columns are shown by default. You can CHOOSE these yourself, of course. Just right-click on the column header to pick what you want shown. However, by default, in the Active Processes tab, I have too many memory metrics, and not enough other data. I'll be changing all this around. I do apologize if this causes your settings to be reset. This will be in .38 or later most likely, as I also am ADDING another metric - I/O. Now, this represents I/O of ALL TYPES, so it is not as useful as you might think, but still, it will be shown.

[Jeremy Collake]

From here on out I will start documenting CHANGES as well ... and get that Intro to v6 doc done ASAP.

[Tarnak]

Just tried to update,  but the automatic updater says 6.0.0.37 beta available, and will not update.  This is with XP.

[Jeremy Collake]

Just tried to update,  but the automatic updater says 6.0.0.37 beta available, and will not update.  This is with XP.

Are you saying you are stuck with the previous alpha, as v6.0.0.37 beta is current, of course. I am re-uploading alpha auto-update builds. Try again.

[Tarnak]

Are you saying you are stuck with the previous alpha, as v6.0.0.37 beta is current, of course. I am re-uploading alpha auto-update builds. Try again.

Yes...I have tried at least 5 times to update. However, I am trying to update from v5.1.1.1.   Is that the reason?

[Jeremy Collake]

Yes...I have tried at least 5 times to update. However, I am trying to update from v5.1.1.1.   Is that the reason?

Yes, that is the cause. My batch file is wrong. I am going to re-upload them in about 5 minutes.

[Tarnak]

Yes, that is the cause. My batch file is wrong. I am going to re-upload them in about 5 minutes.

OK...I'll wait.

[Jeremy Collake]

Ok, it should work now. Sorry about that. The alpha -> beta switch caused some confusions here in the upload scripts.

[Tarnak]

Ok, it should work now. Sorry about that. The alpha -> beta switch caused some confusions here in the upload scripts.

Yes!...got it.

[Jeremy Collake]

Thanks, I also confirmed here in tests. Sorry again about this mishap. Many were likely confused for the 3+ hours. Oops ;o.

[Tarnak]

Glad I could help.

[nereis]

I was able to make ProcessLasso close/restart when trying to remove a selected No Sleep Process, sleep type prevent only display if that matters.
The process selected remains after ProcessLasso restarts.

[Jeremy Collake]

I was able to make ProcessLasso close/restart when trying to remove a selected No Sleep Process, sleep type prevent only display if that matters.
The process selected remains after ProcessLasso restarts.

Thank you. That was a crash, and since you provided the exact code path, I will isolate it immediately.

[Jeremy Collake]

No sleep - Crash in that dialog isolated and FIXED, and I have improved the appearance of that listview, standardizing it with the rest of the program (an oversight). Be in .39 when released.

[Jeremy Collake]

Lock Theme - Now implemented, in next beta.