Bitsum Community Forum

General Category => Process Lasso => Topic started by: edkiefer on June 13, 2013, 01:41:48 PM

Title: "Log process launches" menu position can not be unchecked [FIXED-06060013]
Post by: edkiefer on June 13, 2013, 01:41:48 PM
As title says , log process launches can not be disabled under config and log settings in 6.6.0.12
Title: a small bug
Post by: blackps on June 13, 2013, 02:53:25 PM
There is a problem when you try to remove the logs from process launches the box remains selected and you can see the launches from some programs.
Keep up the good work,the program is great!!!


Thanks!
Title: Re: "Log process launches" menu position can not be unchecked
Post by: Jeremy Collake on June 13, 2013, 05:16:22 PM
Thanks for reporting that! The bug was caused in v6.6 as I made a modification to the settings code, to couple this setting with the logging of terminations. There was a mistake that slipped by code review. I just fixed it, so it'll be addressed in the next release. This is an important option since many users will probably choose to disable it.
Title: Re: "Log process launches" menu position can not be unchecked [FIXED-TBR]
Post by: edkiefer on June 13, 2013, 05:43:13 PM
yup, that is why i checked , I like it off as to me every process list is not needed unless I am looking for something funny .
Title: Re: "Log process launches" menu position can not be unchecked [FIXED-TBR]
Post by: BenYeeHua on June 13, 2013, 11:13:17 PM
Like the updater for auto-update. :)
Or your friend are using your computer, you want to know which software he has launch. ;)
Title: Re: "Log process launches" menu position can not be unchecked [FIXED-TBR]
Post by: Jeremy Collake on June 14, 2013, 03:41:20 PM
Some posts lost in a hiccup during unnecessary server maintenance :o.

Confirmed fixed in v6.6.0.13+
Title: Re: "Log process launches" menu position can not be unchecked [FIXED-TBR]
Post by: BenYeeHua on June 14, 2013, 06:59:07 PM
Quote from: Support on June 14, 2013, 03:41:20 PM
Some posts lost in a hiccup during unnecessary server maintenance :o.

Confirmed fixed in v6.6.0.13+
That fine. :)