not being able to determine the origin of the problem with the little information, what I can suggest is to simply block the screenshot in all circumstances if it is indeed of origin due to an action since first
by redefining the function which calls on the screenshot primitive not only will the message no longer appear but no image will be created on disk.
in zip form, it is obviously a ux which will be used in the directory dedicated to this use.
it's minimalist but can temporarily solve Gjon's problem without any change on his primo
Bookmarks