@Konstantin-Tokarev said in Multiple, identical instances of WebView, dynamically created:

Approach with multiple views is optimal when you want all those pages to be present on screen at the same time, or have indpendent "tabs" like in a browser with separate navigation histories and possibility to do background work like playing music

This is about what we do. The screen is divided into various sections that are used for various menus, sub-menus, lists ... and more. These need to be loaded and shown/hidden separately or at the same time. The GUI is completely based on webpages with html/css/php/js.

I have it working pretty smart now, though there are some limits like a key can not be sent to a webGUI that is hidden for instance, which would be great to preload a GUI section before showing.

@kshegunov Thanks I will try that.

@SGaist
Thanks,

I looked into QSignalMapper, but it seems to have limitations, for example you can only pass one parameter and you can really just map one slot/signal.

I could probably make it work by passing a structure (and register that with the meta compiler), and then use multiple QSignalMappers... but, at least for my case, I find that creating my own object to be much simpler both to implement and to read.

Hi @neovius and Welcome,

When i change the backlight slider, the signal is emitted, and received. but i still get the warning when starting the application :

That is because you are creating QML component before setting the context property and thus naturally it wont be able to access that method at very first time.

http://doc.qt.io/qt-5/qtqml-cppintegration-exposecppattributes.html#exposing-properties
http://doc.qt.io/qt-5/qtqml-cppintegration-exposecppattributes.html#exposing-methods-including-qt-slots

@t3685 ahhhh, so simple!, I was trying to use the wizards to add projects - it literally is just a .pro file with a list of sub-dirs where the next level of .pro files are! - I am sure they don't explain it in those simple terms in the docs : (

Thanks for persevering with your answer, up-voted accordingly : )

@pmh4514

maybe you can use the QDesktopWidget

int QDesktopWidget::screenNumber(const QWidget * widget = 0) const Returns the index of the screen that contains the largest part of widget, or -1 if the widget not on a screen.

@SGaist

Thank you very much for your tips!
I probably should give up on the serial thread. It is beyond my ability to play with that problem.