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 Coldblackice, July 27, 2015, 09:13:20 PM
Quote from: edkiefer on July 27, 2015, 09:35:39 PMI could be wrong but currently a process needs to be running to get path to open location AFAIK .
Quote from: Hotrod on July 28, 2015, 01:15:44 PMIf the command line is recorded in the log entry, isn't the location already known? All we are missing is the ability to jump to that location.
Quote from: Jeremy Collake on July 28, 2015, 02:59:09 PMYes, I can add this, no problem .BTW, you will *love* one new feature I am working on, can't mention it yet though. Totally revolutionary.
Quote from: Jeremy Collake on July 29, 2015, 02:04:31 AMNo, it's not sarcasm, it is trivial to add since I specifically record the executable pathname in the log.
Quote from: DeadHead on August 01, 2015, 03:53:59 AMI'd like to have more or less the same functionality in the Actions log window as in the All processes window, if possible.
Quote from: Jeremy Collake on August 05, 2015, 12:28:11 PMI hear you on duplicating the context menu of the processes tabs in the actions log. I agree, that would be helpful. Definitely I will keep that in mind. I'm pretty sure you both, and everyone, will be fully satisfied with my mid-range plans, which do something super-cool and will sort-of take care of this request. Yes, I'm being vague, so sorry. In the interim, I'll do what I can!
Quote from: Jeremy Collake on August 13, 2015, 03:11:59 PMAlright, I've added this in to internal betas, but it will be a bit before I publish - lots of testing and code review to do.The old log format included the command line, which *usually* includes the executable pathname as argument 0. However, this isn't always the case.So, for robustness, I've expanded the log (new format) to include the executable pathname. There's also a new row in the actions pane log view, and LogViewer.All in all, a decent size modification, but a good one for future additions.