Skip to content

Language Bindings

You're using Qt with other languages than C++, eh? Post here!
853 Topics 3.3k Posts
  • Custom scrollbar doesn't translate to pyqt from designer

    Unsolved
    6
    0 Votes
    6 Posts
    705 Views
    SGaistS

    Tested on a Mac with PyQt installed through conda. Package is pyqt-5.12.3.

    The scrollbar is changed.

    Note that your code cannot be run directly, it's missing a QMainWindow instance as well as the QApplication part.

  • 0 Votes
    3 Posts
    659 Views
    2

    Thanks for the reply @SGaist. What I wanted was to update some data (in form of text) from python backend, most of the tutorials I saw were based on using signals and slots. were as I only needed a slot to read without any triggering signal. Though I've been able to finally figure it out and spending this much time actually made me understood it more. I used QTimer to refresh the backend function every half a second.

  • Rust bindings

    Unsolved
    4
    0 Votes
    4 Posts
    838 Views
    artwawA

    @Olivier92m Then just include that library in your code, assuming it has the right bindings for c++? if it ain't then I don't know, as far as I can't tell you can't make it work.
    If you're about to compile something c++ linking to the said library it has to have c++ header files, you know.

  • Can we change subtitle size and font ?

    Unsolved
    2
    0 Votes
    2 Posts
    301 Views
    SGaistS

    Hi and welcome to devnet,

    From the looks of it, there's nothing related to that.

    You might want to check the bug report system to see if there's something related and if not, open a feature request.

  • 0 Votes
    10 Posts
    900 Views
    A

    @SGaist Thanks for advice, I will try to use them.

  • 0 Votes
    3 Posts
    638 Views
    N

    @SGaist Thanks for the reply. Unfortunately, Deno's event loop isn't exposed, at all. It's just calling functions from a C ABI using dlopen().

  • This topic is deleted!

    Unsolved
    1
    0 Votes
    1 Posts
    6 Views
    No one has replied
  • Shiboken - Signals don't work

    Solved
    2
    0 Votes
    2 Posts
    445 Views
    V

    Turns out Shiboken shouldn't do anything for signals and let PySide setup the signals using the MOC data. Shiboken generates bindings for signals as if they were plain methods and shadows the actual signals. I ended up wrapping the signals with an ifdef:

    #ifndef BINDINGS_H Q_SIGNALS: void positionChanged(qint64 position); #endif
  • Use C# DLL and QT C++

    Unsolved
    2
    0 Votes
    2 Posts
    628 Views
    SGaistS

    Hi,

    See this stack overflow answer for several possibilités.

  • Translation of text from controlscript in maintenancetool

    Unsolved
    1
    0 Votes
    1 Posts
    321 Views
    No one has replied
  • Qt 6 LinguistTools for Android and iOS is missing

    Unsolved
    1
    0 Votes
    1 Posts
    360 Views
    No one has replied
  • 0 Votes
    5 Posts
    585 Views
    D

    Thank you for the reply .

    I am new to Qthread and comfortable with pthread, that is the reason behind I used it in my code.

    Let me go through the link and use qthread.
    Thank you for the sugesstion.

    If possible Please share me some tutorial links for qthreads which helps to build pipeline

    Thank you,
    Dhivya JR

  • This topic is deleted!

    Unsolved
    1
    0 Votes
    1 Posts
    4 Views
    No one has replied
  • 0 Votes
    5 Posts
    758 Views
    M

    @SGaist Huh I've read a little about that QListView and in conjunction with setViewMode(QListView.IconMode) I believe It can do the intended job I'll try that later when I have a little more free time for it and update. Thanks!

  • Shiboken - Problem linking to shiboken2.abi3.lib

    Unsolved
    4
    0 Votes
    4 Posts
    788 Views
    SGaistS

    It might be that you are linking to a static library (just a wild guess here).

  • Pysyde/QTableView: openPersistentEditor works only once?

    Unsolved
    11
    0 Votes
    11 Posts
    4k Views
    SGaistS

    There's no need to close them first.

    The issue here comes rather from the replacement of the delegate. There's no need for that. If you just set it in the constructor and trigger the persistent editors when you add a line, you should be fine.

    One thing that might be worth checking is why replacing the delegate does not close de persistent editor. I do not know whether it's on purpose as you asked for a persistent editor after all.

  • Controlling QT C++ Project from Python Script

    Unsolved
    4
    0 Votes
    4 Posts
    473 Views
    SGaistS

    Did you consider implementing an IPC solution ?

  • Problem with PySide6 and QtWebEngineWidgets module

    Solved
    9
    0 Votes
    9 Posts
    13k Views
    S

    @eyllanesc :ModuleNotFoundError: No module named 'PySide2.QtWebKitWidgets'

    how can i resolve it?in ubundu 20.04,python 3.8.5

  • PySide2 QToolButton stylesheets

    Solved
    2
    0 Votes
    2 Posts
    452 Views
    I

    Ok so I found out that I had to use MenuButtonPopup as value

    QToolButton[popupMode="MenuButtonPopup"] { padding-right: 20px; }
  • 0 Votes
    3 Posts
    2k Views
    L

    I confirm the same observation, that the script runs with PyQt5 (pyqt5 5.15.4) installed via pip and fails when run with PySide2 (PySide2-5.15.2) installed via pip:

    QObject::moveToThread: Current thread (0x22b951c64b0) is not the object's thread (0x22b951c6c50). Cannot move to target thread (0x22b951c64b0) qt.qpa.plugin: Could not load the Qt platform plugin "windows" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: direct2d, minimal, offscreen, webgl, windows.

    Following the advice of this thread (https://forum.qt.io/topic/93085/qt-python-development-pyside2/6), I removed the PySide2 installed via pip and installed the version via conda-forge (v 5.13.2) and was able to run the script. So, it appears a matter of packaging/dependencies rather than a strict inability for PySide2 to handle it or something related to the version.