Hi and welcome to devnet,

If you positioned everything by hand then you either have to redo that or position your widgets in your code for example in the resizeEvent method.

Otherwise, the recommended way to work is to use layouts which automatically adapts to the size of your widget.

@rnayabed Which OS (and version) are you running ?

If you are trying to launch the application via SSH then display it on your host's display, have you tried export DISPLAY=:0 on your SSH terminal?

@Zwenig die einfachste Methode ist der package manager.

den findest du eigentlich vorinstalliert in der Menüleiste, einfach nach Creator oder QtCreator suchen und installieren.

darüber bekommst du auch eine version von Qt (Bibliothek), sollte neuer als 5.11 sein, also sollte dein Programm damit auch kompilieren

Also there is a new instruction for Rasp + Qt6:
https://wiki.qt.io/Cross-Compile_Qt_6_for_Raspberry_Pi

Even not using yocto but buildroot the concepts of what is required to make rpi boot faster are there. Also using Qt application.
https://www.furkantokac.com/rpi3-fast-boot-less-than-2-seconds/

@ElPadre
no i dont couldnt find an example, but i think you can follow the mediaendpointconnector test implementation:
https://github.com/KDE/bluez-qt/edit/master/tests/mediaendpointconnector.cpp

@sbartolett said in Undeclared QMetaObject::SuperData:

Not sure if this error is caused by an incompatibility of versions or not. T

At leasr you should not mix them. Remove the 5.15.5 stuff from your build system (did not say what you're using).

How did you come to the conclusion that the image does not support that module? Looks like socketCAN will support that module so as long as socketCAN is part of that recipe then you should be okay.

Hi and welcome to devnet,

That's because you try to access a standard member variable from a static function.

Take a look at the ir_receiver example of the pigpio project. It shows how to use a class with the callback with gpioSetAlertFuncEx.

@Marek-Stocki
Wait, wait! You absolutely do not want to move a Python3 application back to Python2! Trust me :)

Even 26 seconds startup is quite unacceptable. Start up should be like ~1 second!! There is something wrong.....

@jsulm said in Raspberry pi App works correctly from SSH but not from local command line:

window manager

hi, Thank you for the fast reply. Fairly new to raspberry pi.

What i did was to :

download a full image of Buster and flash it on a sd card; Boot to Desktop Install qt following this tutorial : https://www.kampis-elektroecke.de/raspberry-pi/qt/ Run App from ssh Run app from raspberry pi command line (not ssh)

How can i check for window manager ?

Thank you

Then one way would be to use QWebChannel.

@Yalimyulad said in Post installing Qmake for new devices:

Is it possible to somehow copy the Qmake I have built from raspberry pi to my desktop?

Nothing is physically stopping you, but it won't work.

qmake is created and specific to the Qt FrameWork/Compiler used for that framework.
The compiler on your pi is not the same as the one you would use for cross compiling

If you want to really cross compile for the Pi , you will have to jump through some loops.
There are some guides out there for example this wiki entries

https://wiki.qt.io/Raspberry_Pi_Beginners_Guide
https://wiki.qt.io/RaspberryPi2EGLFS

I somehow workaround it.
On the RaspberryPi I created a bash script in /usr/bin:

/usr/bin/x5

#!/bin/bash xhost +local: sudo /home/pi/adas0002 --platform xcb

I made it executable and then on my Desktop-Pc in Qt-Creator
I have "/usr/bin/x5" in "Alternate executable on device".

Now my application starts with root even without invoking any terminal.
I know this is very bad in security point of view but I dont care on my little offline
Raspi...

I eventually found out that those changes mentioned in the links in the last post require you to set "QT_IM_MODULE=compose" but even then composing didn't work.

That being the case, I've reported a bug: https://bugreports.qt.io/browse/QTBUG-79097

I'm keeping this as unanswered until there is a workaround or a fix, but if you do not need dead keys or composition, just setting the XKB_DEFAULT vars and ensuring you are using libinput/xkbcommon should be enough to get your keyboard layout "working".

Hi,

I'm the author of QtUsb.
The modular version (0.5) is on beta and not available on ppa (0.4.2) yet. I'll work on that.

Feel free to open issues on github if you find any bugs.

Edit: it should be good for bionic and newer.