-
Notifications
You must be signed in to change notification settings - Fork 4
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
Towards a new visualea on PyQT5 and Python 3 #14
Conversation
…roblems. Done pyrcc2to3
just QtGui to QtWidget when relevant, visualeagui not working yet |
….vpltk.qt import qt and from openalea.vpltk.qt.QtGui import *
forgot some QtCore, changed qt.QtCore.SIGNAL to QtCore.pyqtSignal And removed all import as: |
I will replace the pyqtsignal with the native interface: self.connect(self.savescut, QtCore.pyqtSignal("triggered()"), self.save_changes) by self.savescut.triggered().connect(self.save_changes) |
…nted line just to get open the visualea window
I got the visualea main window open with the python shell working with, for example, very simple numpy functions. But to reach that, I commented some lines referenced with # F. Bauget 2023-01-18. Just to see . |
…r from func_tools
…h methods with a signal/slot
…abColorMap, Global parameters in weberpenn, species in weberpenn, the value was set to the index not the text
… now I got the node becoming red without crash
…d oalab, and oalab had referencies to visualea already
No description provided.