[Development] Are there any limitations on implementing the changing of the screen for a QWindow on systems using EGLFS?

Laszlo Agocs laszlo.agocs at qt.io
Tue Jul 26 15:33:38 CEST 2016


Lack of contributions and suitable hardware setup. There was a patch for making the target screen configurable via an environment variable which never made it to integration. We are now reviving it for 5.6 at https://codereview.qt-project.org/#/c/166117/


Additional patches for discovering and exposing all available screens as separate QScreens are welcome. Not entirely sure about the feasibility, especially when it comes to discovering and monitoring the connected outputs, but it is definitely worth a try.


Best regards,

Laszlo


<https://codereview.qt-project.org/#/c/166117/>

________________________________
From: Development <development-bounces+laszlo.agocs=qt.io at qt-project.org> on behalf of Verebélyi Viktor <vviktor2 at gmail.com>
Sent: Sunday, July 24, 2016 8:28:15 AM
To: development at qt-project.org
Subject: [Development] Are there any limitations on implementing the changing of the screen for a QWindow on systems using EGLFS?


I looked at the code for the EGLFS BRCM integration and the screen it uses is hard-coded. After trying some test code for Dispmanx it seems that it is fairly straight forward to change the screen it uses.

My question is: Are there any limitations to implementing the functions that would allow us to change the screen using QWindows->setScreen()?

The reason for why I'm asking is, because I'd like to implement this, but I'd like to know whether if this is not implemented beacuse of some limitations or because of lack of intrest/contributors?


--
- Viktor Verebelyi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160726/331f6a15/attachment.html>


More information about the Development mailing list