Linux/PROCESSOR-SDK-AM335X: Test the qt5 problem of ti-processor- SDK -linux-rt-am335x-evm-05.01.00.11

Hello Krunal Bhargav34
I ran my application with PLSDK 4.3.0.5 running weston 1.11,There is no such mistake, but there is another problem:
In my application  test in PLSDK 4.3.0.5 (runing weston 1.11) , and it was found that the shortcut key of the sub-window after F1 pop-up window was not effective, and the shortcut key was only valid after clicking the sub-window with the mouse, but this problem did not exist in PLSDK 5

I'm sorry for taking so long to reply. I ran qt5 in PLSDK 4.3.0.5. There was no error in the shortcut key, but as I said: In my application  test in PLSDK 4.3.0.5 (runing weston 1.11) , and it was found that the shortcut key of the sub-window after F1 pop-up window was not effective, and the shortcut key was only valid after clicking the sub-window with the mous.

You can use the engineering test I uploaded to the attachment earlier

Thank you. Looking forward to your solution

Hi,Krunal,

To verify that the X11 SDK Qt has the same problem, I built the SDK of x11 through processor- SDK -04.01.00.06-x11-config.txt to test qt.

The test results are as follows:

In the main window by a shortcut key to open the window, closed or hidden child window and return to the main window, at this point in the main window, the shortcut key to open the child window shortcuts can't use a child window (the child window at the top), but the main window of the shortcut you can use, this problem cause we can't use the shortcut key switch at the top of the window ! Is there a solution to this problem?

Attachment untitled-x11.zip is my test project(You can directly run the execution files in the attachment package)

untitled-x11.zip

Hello Regards

However, PSDK 5.0 still cannot solve my second problem. What should I do? If qt's QDialog::exec() cannot be used, our project's warning window will not work properly and will cause many operational problems.

The specific test results are as follows: after using QDialog::exec() mode to display the child window, the child window should be at the top level, and the mouse cannot operate the parent window, but the test on PSDK5 found that the mouse click on the parent window will cause the child window to be overwritten by the parent window, resulting in the child window being unable to operate.You can use -platform linuxfb or eglfs to start my project and compare it to running it on wayland.This problem is fatal for qt window operations, where HMI cannot be manipulated. If you need my assistance in testing, please inform me by email.

My second question:

2. Clicking on the parent window while using the exec() function to display the child window returns the focus to the parent window, which is overwritten by the parent window(use waylan westion)，

but But using -platform linuxfb or eglfs is normal.

Check the qt help documentation for an explanation of this function:

int QDialog::exec()

Shows the dialog as a modal dialog, blocking until the user closes it. The function returns a DialogCode result.
If the dialog is application modal, users cannot interact with any other window in the same application until they close the dialog. If the dialog is window modal, only interaction with the parent window is blocked while the dialog is open. By default, the dialog is application modal.

Hi Qing,

Are you planning on running the GUI as a full screen or a window application? When we run the application using linuxfb/eglfs, we are using the fullscreen mode. However, Weston acts as a window manager and is creating multiple windows that you are able to switch between using a mouse.

Regards,
Krunal

hello Regard,

I understand what you mean. You mean that if the GUI is set to full screen, there will be no problem for me, but we cannot use full screen for some GUI.For example: qt warning window and our own qt digital soft keyboard can not be full screen, because it will be very ugly, our users do not accept. The method you give cannot solve my problem, and your method cannot effectively show the original function of int QDialog::exec().

This is the code I modified for your test project. I added a warning window test.0160.test_code_v1.tar.gz

Hello Qing,

Based on my understanding, once the child window is activated, you would like to ignore the mouse/keyboard events. With regards to the function "QDialog::exec", you could post Qt related questions on the qt forms:  

Regards,

Krunal

Hello Regards

I don't think so. The PSDK version below PSDK 5.0 does not have this problem.

I think it is either the docking problem between PSDK driver and wayland, or the problem of wayland version. I do not know about psdk5 and psdk4 or the psdk4 or lower version of PSDK driver, I just guess.Wayland, as a window system, cannot correctly run the original features of qt when running qt, which I think is incorrect.

Hello Qing,

I believe this seems to be a problem with Wayland/Weston because I was going through the reported bugs and saw something similar to what you are observing. Here is the link:  

Regards,

Krunal

Hello Qing,

I will be closing the thread and I will be helping you address your issues in the following thread:

Regards,

Krunal