I have already sent Berry 2 test reports and have just now sent him a third - the latter about what I have termed "the Systray problem".
The symptoms are that sometimes, after being minimised/closed to the Systray, NF disappears from the Systray, though the process appears to continue.
The collage of screenshots below is intended to explain it, and what I could find out about it.
I am providing the screenshot not so much as to describe an apparent error/bug, but rather to demonstrate how useful Screenshot Captor can be in problem analysis cases like this - where "a picture is worth a thousand words".
The picture is comprised of a sort of collage of different screenshot bits, starting with the first - which was of the Task Bar
and Process Hacker
window (which were side-by-side) - and then overlaying other screenshot clips and adding a text box and arrows, and expanding the canvas in SC (Objects-->Expand canvas to fit objects
I'm sure I could have made it look nicer, if I took the time, but the thing is it would have been difficult for me to do this without using SC. SC really is a superbly crafted and useful tool for such purposes.
The only constraint in using SC in this case seems to be in taking any screenshot of an area of the screen which contains a system pop-out window - and there were 2 such instances in this case. SC couldn't take such a clip without closing the pop-out window first, every time I tried it. The Windows Snipping Tool
and the ABBYY Screenshot Reader
weren't any better, but the OneNote Screen Clipping
tool did the job just right as it freezes the on-screen display as soon as it is invoked, allowing the user to take their time to frame the section clip.EDIT 2015-05-12 0146hrs:
Having rebooted the laptop, I am pleased to report that the apparent "constraint" in SC no longer applies.
In both cases, SC captures the stuff after nicely freezing the screen.
The only thing I can think might have caused it was my TouchPad mouse, which had been behaving very strangely, so I uninstalled it and restarted the laptop, whereupon the TouchPad was auto-reinstalled. The TouchPad is now working fine, and so is SC.