@SGaist Thanks for your reply. I appreciate that the tool itself wouldn't dictate the licence terms, but was curious as to whether it said anything about the Qt Company's view in whether the resulting package would be LGPL compliant from the perspective of the PySide and Qt Libraries. However, since that original message I tried out pyside6-deploy and realised that there's no way the resulting package could be compliant (in terms of allowing modified versions of the libraries to be swapped in) due to its use of Nuitka's onefile option.

Hi and welcome to devnet, I think this article is still valid.

@Improv-Jester Upgrading to 6.6.1 has fixed it! Thankyou for taking the time and for you sage advice.

@CristianMaureira Thanks I do it now like you said it, and added a comment for PyCharm IDE to not remote these imports when I run the Optimize Imports Refactoring tool. # noinspection PyUnresolvedReferences from src.examples import CpuLoadModel, NumberGeneratorSignalbased, NumberGeneratorPropertiesbased, UserModel # noinspection PyUnresolvedReferences from src import RecipesModel

@Niccolo-v showing the videos would require a custom delegate. As for the issue with a high count of widget, I can't comment without a reproducer.

@LREGS said in Accurate Button Placement in QDesigner: However, when I'm placing them in QDesigner it's not possible with my current knowledge to place them exactly in the holes of the image because it seems the center of the label needs to be anchored to one of the background dots in QDesigner. This is probably the snap to grid behavior. From the menu toolbar: Tools -> Form Editor -> Form Settings ... Check the Grid checkbox, and then uncheck Snap. @SGaist's suggestions are likely easier to deal with in the long run.

@Munter Thank you for your reply. Can I ask specifically in what direction I should go, what can I use to create a custom viewport?

@britesc Qt connections must be made between instances of the signalling class and the slot class. You do not show where, but somewhere you create an instance of tab_initial_setup class. (It might be in your self.setupUi(self) if you created it in Designer, I don't know; perhaps not since tab_initial_setup is its own class.). You need to find that. Let's say somewhere (in MainWindow or Ui_MainWindow or setupUi()) you have something like self.tab = tab_initial_setup(). Then you would need: self.tab.signal_pb_previous.connect(self.signals_received) in somewhere like MainWindow's __init__() method, after the self.tab = tab_initial_setup() has executed.

@SGaist Sure https://bugreports.qt.io/browse/QTBUG-118501

Thanks !

@britesc How about doing this in Python, nothing to do with Qt? Maybe https://stackoverflow.com/questions/53107367/convert-calendar-date-to-julian-date-python ?

@JonB said in QFileDialog.getExistingDirectory default directory: Try creating an instance of QFileDialog and call QFileDialog::setDirectory(const QString &directory) on it, to see whether that works instead of the static QFileDialog.getExistingDirectory(). That works OK. Thanks a lot.

@BrantFF said in How to set QProgressBar widget in vertically from Qt Designer?: It will return to default value( here is Horizontal ) when I change other attributes. Give an example of exactly one further change which causes Vertical to get replaced by Horizontal. And if it really does that the version of Qt Creator you are using. OIC, Qt Designer: v6.5.0. Give the change example (e.g. does it happen if you uncheck textVisible? does it change if you pick some other widget and change one of its attributes, so that you are saying any change at all causes reversion?) and ask someone with that Designer version if it happens to them.

@friedemannkleint I tried all that, I tried different versions of virtual environments. Finally I switched over to PyQt6 and now it works flawlessly.

@kaushikv Why will I use that when QML already has a treeview and the model isn't the problem? Plus I tagged thi question as Qt for Python.

@go4tli Indeed, it was very well spotted by @SGaist, I don't think I would have noticed it! Python could do with an override keyword to catch this, which it lacks. If you are interested for the future In Python, how do I indicate I'm overriding a method? or https://pypi.org/project/overrides/ suggest some code snippets which would catch such a mistake....