nevermind, I just found it. now my #NVDA should be logging debugging. now should I restart NVDA to make it start doing it, or will the log file change right away to having the debug stuff?
The log level changes straight away, but I recommend restarting both so you can ensure you do it with add-ons disabled, but also because then you can safely send your log knowing it concentrates on the issue - if you were using your PC for ten hours before you started documenteing the issue, it might need a lot of scrolling and searching in the log to find the right spot - so the shorter the better.
@NVAccess the problem is that sometimes this thing is so randum it might take 10 hours for it to happen. sometimes not that long, but yes, sometimes it doesn't show up for a day or two. it ijust that when it does, it can hang around until I restart NVDA.
That is often the nature of bugs unfortunately - per my comment about a clean log, obviously that is ideal, but if you only hit it after ten hours use, then so be it, we can likely work with that :)
NV Access
in reply to JamminJerry • • •JamminJerry
in reply to NV Access • • •NV Access
in reply to JamminJerry • • •