-
Notifications
You must be signed in to change notification settings - Fork 96
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
TypeErrror on Windows with some traitsui / mayavi tools #1853
Comments
Let me follow up here: Deletion of elements is not possible too. A window pops up and disappears so quickly I cant make out what it says. I think I traced it back a bit:
If I remove Any ideas on this? |
Thanks for the report. Unfortunately I can't currently replicate the behaviour in pure TraitsUI (on Mac, with PyQt 5.14.2). Indeed, However the lines in 1007 onwards shouldn't be called until after all menu interactions are done: I think that the The standard execution flow should be something like:
with no opportunity to resume execution after the Can you install TraitsUI from the main branch and see if it still occurs? Also, can you try with a different version of PyQt5 or PySide2, as it is possible that this is hitting some bug at that level. Also it is possible that Mayavi is doing something nonstandard in its tree view widget which may override this analysis. |
I added some prints around the reset and as soon as I interact, both are called on appearance of the menu. This is, however logical since at the other issue @prabhuramachandran came through and explained that my event loop was not running. So this obviously stops Oh and btw:
Can you produce a MWE just to test TraitsUI? |
Hi,
let me link this from mayavi, I did not get any answer there and I feel this might be related: enthought/mayavi#1127
In short, using mayavi works (examples, custom scripts) but when accessing the tree to change any property, the following occurs and crashes the current window:
Any help to pinpoint me for a fix? Seems to be that
self._data is None
which is not supposed to happen...?The text was updated successfully, but these errors were encountered: