Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PyOtherSide does not allow closing to be interrupted. #79

Open
andyfozzy opened this issue May 1, 2017 · 0 comments
Open

PyOtherSide does not allow closing to be interrupted. #79

andyfozzy opened this issue May 1, 2017 · 0 comments

Comments

@andyfozzy
Copy link

I am currently working on an application with sub-windows for viewing information about individual parts of a whole system. both the main application and the sub-windows use pyotherside. I have discovered that if I open a sub-window and close it again before all python modules in the Python element have been imported, it causes issues when the sub-window is opened next time. The problem is that the python processes from the original window cannot be stopped on closing and continue running. Depending on the exact set-up of the machine this can stop updates coming to the sub-window through python, or even a crash the whole application.

I have noticed this only in Windows, though I suspect this is just because the Windows version takes longer to import modules.

I would appreciate being able to stop python doing any of its atexit processes until I allow it to procede. This can be done on the QML side by setting close.accepted to false, but this seems to have no effect on pyotherside.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant