nswindow drag regions should only be invalidated on the main thread

Nswindow Drag Regions Should Only Be Invalidated On The Main Thread Code Works Fine

If so, it calls another Python script (call it program.py) that takes the new file as input and uses matplotlib to plot graphs.

However, instead of plotting and saving images, I get the resulting output.

Does this mean I cannot create an automated script for detecting new files and running a matplotlib analysis on the new files O.

It works now (It might be nice to have some check in matplotlib so that it doesnt crash the kernel when faced with that situation) edit: I see there is a pull request for it:):).

From here issues are either reopened, or are closed.

The frustrating thing is that Ive never had this problem before; it only just started happening now.

I can go into fullscreen, but when I do, it only shows the display (small) at the bottom left corner of my screen and everything else is black.

I also cant get a screenshot of this for some reason- it wont let my computer do it.

One displays a GUI and the other gets input from a scanner and saves data in an online database.

Nswindow Drag Regions Should Only Be Invalidated On The Main Thread Code Works Fine

The code works fine on my raspberry pi but if I try it on my MacBook Pro (Catalina 10.15.2), I get the above mentioned warning followed by my code crashing.

Your Python on your Raspberry PI still allows invalidating NSWindow drag regions outside the Main thread, while your Python in your MacBook Pro already stopped supporting this.

You will likely need to refactor your code so that NSWindow drag regions will only be invalidated on the Main thread.

Provide details and share your research But avoid Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

Not the answer youre looking for Browse other questions tagged python python-3.x multithreading macos nswindow or ask your own question.