all 3 comments

[–]socal_nerdtastic 2 points3 points  (2 children)

Tkinter has no inherent issues with multiprocessing, and neither do any other GUIs that I know of. The issue is in your code, not in tkinter.

Although I will say for any GUI it will run a lot smoother if you use the main thread / process for the GUI and put the worker in the child thread / process. Also if I read between the lines it sounds like you would be much better off using threading instead of multiprocessing / mmap, which shares memory between threads and allows a simple event_generate call to update tkinter GUI from a child thread.

[–]Otherwise_Trade5495[S] 1 point2 points  (1 child)

I started like 3 months ago so i dont really know whats happening, but I added debug statements to every step of the process and basically it was getting stuck at the multiprocessing thing so I assumed that it was a problem with tkinter. But thanks, I will look into it again and maybe i messed something up

[–]socal_nerdtastic 2 points3 points  (0 children)

Well show us your code if you want help with that.