Progress bar Tkinter error about dynamics HOT 8 CLOSED

The master branch of the plugin feature brand new progress bar rewritten from Tix to ttk. It probably require few more touches to eliminate last bugs. Your error seems to be the result of Tkinter not being thread safe, but updating status bar is done with separate thread. I should use Queue object instead.

from dynamics.

Updating progress bar should now be handled in thread safe way. Please test it before I close the issue.

from dynamics.

Sorry for the delay, I was busy and missed the notification about the issue. I still seem to have the same problem on PyMOL 1.6.0 with the latest Dynamics from GitHub. Namely, the exception is thrown and the GUI does not seem to get updated correctly when simulations stop.

from dynamics.

Could you please paste here current error message, as I need to know, which line of code is still not thread safe. Thanks for testing!

from dynamics.

Here you go:

Unhandled exception in thread started by
Traceback (most recent call last):
  File "/apps/pymol/1.6.0.0-x86_64/modules/pmg_tk/startup/dynamics_pymol_plugin.py", line 1063, in bar_update
    root = Tk()
  File "/apps/pymol/1.6.0.0-x86_64/ext/lib/python2.7/lib-tk/Tkinter.py", line 1685, in __init__
    self.tk = _tkinter.create(screenName, baseName, className, interactive, wantobjects, useTk, sync, use)
_tkinter.TclError: out of stack space (infinite loop?)

Please let me know if you want me to repeat the test. Cheers!

from dynamics.

Hi,
Please check if everything works fine now.

from dynamics.

Error is gone now. Seems to work fine now. Thanks.

I noticed a smell glitch though: if I start calculations and have a fatal error of the calculation setup, which effectively stops the calculations, the start button is still pressed as if they were still running. Also, hitting stop and start again in the same calculation window does not produce the error again as if it does not do anything. I just wanted to highlight that as I do not know if this is an expected behaviour or not.

Cheers,

Jakub

from dynamics.

I am glad, that we got rid of this pesky bug. I have moved your new observation to #49 .
Please continue testing software and provide your feedback. I am closing this Issue now.

from dynamics.