I had two instances of 1.4 running as I was working on two projects at the same time and flicking back and forth.
On the active instance I was performing a scan on a raster image and when the scan finished Windows flicked Inkscape to the other instance, so for example, if I was working on a project of a cat and a project of a canary, and i was actively scanning a canary picture on the canary project, when the scan finished i was suddenly looking at the cat project.
I assume the Window Process Id of the inactive window jumped above the active Window Process Id, or something like that.
Beginners' Questions Window_Thread_ Process_Id bug on Win10?
Inkscape.org
I had two instances of 1.4 running as I was working on two projects at the same time and flicking back and forth.
On the active instance I was performing a scan on a raster image and when the scan finished Windows flicked Inkscape to the other instance, so for example, if I was working on a project of a cat and a project of a canary, and i was actively scanning a canary picture on the canary project, when the scan finished i was suddenly looking at the cat project.
I assume the Window Process Id of the inactive window jumped above the active Window Process Id, or something like that.
Has this been reported before?
Feel free to search here: https://gitlab.com/inkscape/inkscape/-/issues
Cheers, I didn't realise that existed