@markleo
PySide is not a language. It's just a bunch of Python code bindings to Qt functions written in C++. So your question is just about Python. To which you have answered that "Python is a weakly - typed language".

@jsulm Hi, you can check it on there:
https://zahere.com/microkernel-architecture-how-it-works-and-what-it-offers

The text description sounds like a QMdiArea

@markleo
For IPC you have shared memory, TCP sockets, named pipes, for parent/child processes stdin/stdout, or specifically Qt Remote Objects. All available from Qt and Python.

This looks like your Qt version is way too old. PySide2 also does not support the platform; please use the current version (PySide 6), see https://doc.qt.io/qtforpython-6/gettingstarted/index.html for cross build instructions.

Oups, everything is working only if I select the python interpreter version in Visual studio Code in the right bottom bar and not by using the classic command lines pyenv local / .\env\Scripts\activate
XD

It is not really clear what exactly you did. What is BaseWidgetWindow?
If you're imnplementing a custom title bar then take a look at https://github.com/imitatehappiness/QtCustomTitleBar

@jsulm ahh.. got it 😄. Thank you

@JonB I wasn't even aware my widgets would disappear when dragging it in the middle like that -- but they did as well!

The second link seems to have solved it. Thank you so much for help!

Just in case anyone finds this in the future, here's the Python version:

def dragMoveEvent(self, e): if ( (self.row(self.itemAt(e.pos())) == self.currentRow() + 1) or (self.currentRow() == self.count() - 1 and self.row(self.itemAt(e.pos())) == -1) ): e.ignore() else: super().dragMoveEvent(e)

@PratikTayshete
I'm too new to this to suggest a proper solution... but this seems to work for my for pyside6 to correctly import the _rc.py file

pyside6-uic appUI.ui -o appUI.py --absolute-imports --python-paths ./icons/

Note: When I run pyside6-uic --help I see the following

--rc-prefix Python: Generate "rc_file" instead of "file_rc" import

This suggest to me that you are expected to name of your compiled resource python files to either prefix or suffix with rc_ or _rc respectively.

e5ba5886-00aa-4dac-b61c-9bf28770a84c-image.png

I agree with @JonB that QLineEdit would not be my first choice. We have similar cases where we use a QStackedWidget with a QLineEdit and a slider to switch between the two. In other instances Qt will put an edit widget over the current widget (e.g. in table widgets). These would be the usual approached to solve this problem differently.

However, I would advice against using several stylesheets for your QLineEdit and switching between them. You can have a single stylesheet together with dynamic properties. Have a look at the documentation: https://doc.qt.io/qt-6/stylesheet-examples.html#customizing-using-dynamic-properties
Just use an enum for your different modes and check inside the stylesheet the value of your mode to do different styles.

@ZEZON
Please paste code not screenshots so people can copy from it.

Your code should be working, but I'm afraid it looks like it isn't due to some PySide2->Python issue. https://www.pythonguis.com/tutorials/pyside-dialogs/ for PySide2 even includes same line as you. If you can test under PyQt5 that would confirm.

I don't suppose it will help, but try:

buttons = QMessageBox.Yes | QMessageBox.No mais.setStandardButtons(buttons)

Actually, if you try the above one and it errors please show which of the two lines it complains about, that would be useful to know.

I don't know whether something like

buttons = QMessageBox.StandardButton(QMessageBox.Yes | QMessageBox.No) mais.setStandardButtons(buttons)

would work.

See for example https://www.qt.io/blog/qt-offering-changes-2020

Hi,

Since Qt 5.15.2 contains only x86_64, one thing you can do is start a shell with the arch command so that it runs in x86_64 mode and from there follow the build instructions.

I have had the same error but with another library "libQt5Qml.so.5". I have tried various alternatives, and in my case, that error occurred when I executed a function in QML, which was supposed to create a custom component previously created in another directory, inside main.qml. In the end, the only thing that solved the problem was migrating to QT6. In my case, I was using PySide2, so switching from PySide2 to PySide6 solved the problem. Try using QT6 instead of QT5. Good Luck

@tilz0R in addition to @JonB, don't call self.show in an __init__ method. It's not the role of the widgets to make themselves visible. That is the role of the object or method creating them.

Meh forgot about shiboken2 sigh
shiboken2.wrapInstance(widget_pointer, QWidget)
To the rescue!