-
Notifications
You must be signed in to change notification settings - Fork 253
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
loadUiType usage #237
Comments
We already support one way of importing .ui files which doesn't require @Ahuge However, I'd be happy to know more if you are unable to use Those examples you found are "leftovers" from implementing I see we should update the README for
This is no longer true, as |
IMHO I'm trying to steer people away from loadUiType towards simply loadUi because it's a lot cleaner to use and implement. loadUi unfortunately has a slightly higher overhead though if you're instantiating many ui objects because it's loaded multiple times whereas loadUiType can be loaded once in a module and reused. |
Yeah I did some looking into it for our usage cases and we can just use loadUi. Thanks for the explanation |
Cool. I'll close this then. |
Hey,
I'm going over some code that we are converting and it uses loadUiType instead of loadUi.
In the examples folder there is some code to implement a load_ui_type wrapper it looks like.
Do you have any plans for that code to make it's way into the core Qt.py module?
The text was updated successfully, but these errors were encountered: