rugk 397 Posted September 10, 2014 Posted September 10, 2014 (edited) I noticed a funny glitch in ESS v7 and BETA 8. And I assume that it also happens in NOD32. So here is a small way how you can reproduce this: Open the ESS main window. Now you have to produce a popup. A simple way to do this is to do as I describe in this points: Click on "Scan computer" and "custom scan". Make a scan that will run quickly. I would e.g. suggest to scan the operation memory, because usually this is quite fast. Now click scan and you will see a scan result some seconds later. You will also see this in a popup (usually at the bottom right) Now before the popup disappears minimize or close the main GUI (not the popup). You will see that the popup also disappears and this is the error. You can reopen the main window now and you'll see the popup again now. So there is the error. And yes I know it's really small, but it is an error... Edited September 10, 2014 by rugk
Administrators Marcos 5,446 Posted September 12, 2014 Administrators Posted September 12, 2014 We know, this is by design : )
rugk 397 Posted September 12, 2014 Author Posted September 12, 2014 (edited) We know, this is by design : ) And why is this by design? Has this any useful use? I mean wouldn't it be more useful to display the notification regardless in which stet the main GUI is, so that the notification only is invisible anymore if you close it or it will "fade out" itself? Edited September 12, 2014 by rugk
Recommended Posts