@abiabi
Because Qt Designer/Creator is not particularly Python-oriented.
The accepted solution from @eyllanesc is the way to go, as with his other Python posts.
Hello @Jaime02 ,
Hum I am using poetry and as it is showed in the project, there is no specified version (so it takes the latest if available). It works perfectly out of the poetry world yes for sure, but not in poetry one...
@BGrimaud
If you delete the ui_...py file and resave does that recreate it, and reflect new changes?
Do you have the option to try a newer version of Creator?
Please run your app in debugger to see where that happens
Dear @jsulm,
Thank you for your suggestion. I did execute the application using the debugger; however, it encountered an issue at the first line of the init_gl function, displaying a message indicating "disconnected unexpectedly." Unfortunately, no further information was provided.
Found solution for this problem!
By default, QCompleter object is set to CaseInsensitive and that is what was setting it to the previous entry. With an addition of line like this:
self.combo_box.completer().setCaseSensitivity(Qt.CaseSensitivity.CaseSensitive)
things are working correctly!
We actually provide a tool,
pyside6-project , which defines a simple project file format and can do these steps automatically and can also be opened in Qt Creator.
@RemDup
The alternative way which should work is not to load the stacked widget initially. Show the main window and set off a 0 duration singleshot timer before entering the main event loop. In the slot, which will be run just after the main window (or whatever) is shown, create and load the other widgets.
@friedemannkleint The data that the model provides is not displayed in the tableview. When button is clicked, it should be emitting signal with the model that carries the data, so model=null is turned into model=actual data, then the data should be displayed on tableview. As you can see I've left part of the TableView block empty so someone could suggest the solution to this.
thanks it works closely but not perefect solution because few black pixels are still visible in edges.but its negligible
[image: 73c9289a-9cb8-4d9d-be34-0ee636ef7ac5.png]
I think I finally understand how .ui.qml, .qml and python backend should work together when working with QDS project.
Way I did this was to export component ID as property alias in QDS by clicking @ sign, as shown on screenshot:
[image: 9db015ee-13e0-4bbe-9cc7-0999fc6bfab1.png]
Then this alias should be used in .qml files, such as App.qml in order to access the component in .ui.qml (This was the biggest confusion point for me). Then we can use signals and slots to connect components with backend as usual.
I created a minimal example and can be seen here in case anyone has same issue.
https://github.com/irakliskhirtladze/QML-Demo
