Select Wayland output for QT application - qt

I am running QT 5.11.3 on a TI embedded platform (AM5728). My display manager is wayland 1.16 (weston). The QPA for my application is Wayland-Egl.
The embedded system has both an LCD panel & HDMI output. Both are recognized and treated as independent outputs in wayland.
My question is: How can I programatically choose which wayland output my QT application starts on?
I found that if I use a mouse, the application starts on the output which the mouse is currently active on, but I need to have the application start on the specific desired output (without mouse).
Are there any back-end QPA related calls or settings which can be configured to allow this?
Thanks!

Related

Qt control not working properly in custom Linux

I'm trying to develop a Qt application to a custom linux built with Buildroot for Raspberry PI 4. My goal is to make an GUI through Touch interface and for that I'm using an USB Infrared frame.
My Problem
When I try to interact with a frame, I can move the dial, but when i try to use another dial it behaves like the first pressed dial didn't get released (like when you press mouse 1 and don't release it anymore).
It just stays selected and I can't interact with any other thing in the application.
I run the program using this command :
./dials -platform linuxfb
and here is the frame I am talking about.
What I tried so far
I tried some of the examples provided by Qt that came with buildroot. They seem to work just fine with the mouse in both the Raspberry and in Ubuntu (my PC). Also I tried the same examples in Ubuntu with the touch frame and they also worked flawlessly .
I've set QT_QPA_EVDEV_TOUCHSCREEN_PARAMETERS:/dev/input/event1 , if I don't do this it doesn't even move anything.

In Qt embedded 4.8.4, USB keyboard doesn't work properly

When I start embedded Qt GUI application from a serial port or a terminal via SSH, then type input from wireless USB keyboard, I almost cannot see input on console screen. I have set
export QWS_KEYBOAD=TTY:/dev/tty1
or
export QWS_KEYBOAD=linuxinput:/dev/input/event2
for
/dev/input/by-path/platform-ehci-omap.0-usb-0:2.2:1.0-event-kbd -> ../event2, it doesn't work too.
But If I start my application from console screen which is /dev/tty1, it works fine.
My issue is my application starts automatically after reboot, it doesn't respond to keyboard input. Any ideas?

Is it possible to run JavaFx without X-server?

My plan is to run a JavaFx application on a Raspberry Pi. While the usual way is to start the GUI which is then redirected to the HDMI port, which presents the whole of desktop on the TV.
However, I do not want to see the desktop or anything else, other than the content rendered by my application on the TV. Is it possible to send the rendered output directly to HDMI port?
Yes you need the arm port of java8, where fx renders directly into the framebuffer.

Qt creator remote debugger

I am trying to hook my beagle board to qt creator 2.3.1 running on Ubuntu Linux. I tried to find a good tutorial for this and found that qt documentation has nothing on this.(I do not understand why there is a feature which documentation does not bother to explain how to use). Could some one please explain how to do this?
Cross compile qt for beagle board This post should be at help
Open Qtcreator and go to project tab and select the tools -> options. Select Linux devices and add the device. For this beagle board need to be attached. For the option of host name it is required to add the ip address of the device. Other than this other fields are self explanatory. Test Button would assist in checking the device addition.
Then in the project settings under Run configuration in the Deployment drop-down box select Build tar ball and install.
At this point tool chain and the cross compiled qt version should be added in the qt creator.
Basic procedure should be done by now and when the application is run it should be deployed on the device at the specified location.

Testing Launcher icon on Nokia Qt SDK

How do you test the application icon in the Nokia Qt SDK Simulator? The one which starts when u run the the application from within the Qt Creator.
I like to see how it works & how the sizing works out, but seems there is no App Launcher process as there is in iPhone/Android. Any hints?
If what you want is to have a view of the device menu from which you can launch your app by pressing its icon the simulator doesn't provide a feature like that.
If you want to test your app in a more real enviroment or in device that you don't have maybe the Forum Nokia Remote Device Access could help you.

Resources