@Axel-Spoerl Yes, I have but not this one. Thank you for the link!!

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/

@Olivier92m Then just include that library in your code, assuming it has the right bindings for c++? if it ain't then I don't know, as far as I can't tell you can't make it work. If you're about to compile something c++ linking to the said library it has to have c++ header files, you know.

@mingvv First, you should understand the basics of C++ and object-oriented programming in general. Without it's really hard to get a satisfying result and you will spend most of your time looking for things or trying to figure out how things work (or why they don't). Qt also has Model-View based classes. https://doc.qt.io/qt-5/model-view-programming.html You can communicate with your GUI or other QObject classes using the Qt signal&slot system or using events. For example if you press a button, you will emit the clicked signal. Then, if you connect a slot (= function) to this signal, the function will be called to perform some actions. https://doc.qt.io/qt-5/signalsandslots.html A (simple) snake game in Qt might be a practice to start with. Think about what classes / structure you will need, design your GUI and start writing your code :) Might be helpful: https://doc.qt.io/qt-5/graphicsview.html According the "GUI Code vs Designer" thing: It's mostly a mix of both. Some things just can't be done using the QtDesigner, but it helps a lot creating your basic widgets and your basic design.

QMainWindow::setWindowIcon("name _of_png_file");

@Gojir4 Sure, Thanks for your Help.

I think You're missing most important part here... money. How much was spend on re-brand? I know that some companies do pay big bucks for simple stuff like new slogan / logo etc. and if that's the case here that I can say that QtCompany did overpay. In my opinion this could be easily achieved by one designer over night, but lets be more realistic and assume one month worth of work was put into this, plus changes to WWW / forums etc. so lets extend this to two months and i.e. 3 web developers plus one designer. This give two months worth of work for 3-4 workers. I honestly doubt that within that time solid API could be written for half of features that was pointed out. Also web API do change from time to time so maintenance is also a problem. Imagine situation when commercial customer purchased Qt license and all of sudden i.e. advertisement or analytic modules stops working due to change of API and Qt has no control over this what so ever - this is a risk. Don't get me wrong, I would love to see those features working, even with bugs.

Have experience You need: 10+ years of C++/Qt experience Worked with images and graphics in Qt Worked with ffmpeg, video encoding, etc, have own scripts for this :) Good coding and documentation skills Good English Experience and ability to develop cross-platform applications for Mac OS X, Windows, Linux Knowledge of Git Full CV: http://ua.linkedin.com/in/alekseykontsevich

What PDA device ?

Here's an example of the errors I got. http://hastebin.com/qalutirici.coffee This seems like a false positive or something that isn't in my code (maybe I'm wrong). In each error I got, the "at" is pointing to a function that isn't part of my code.

I've checked, there's currently no option to do it directly with Qt Multimedia. You might want to check the QtAV project.

Thanks so much for taking a stab at it. I tried setting the experimental.preferredMinimumContentsWidth to numbers ranging from 1 to 10000, but it doesn't seem to have any sort of affect for me. I have tried playing around with experimental.page.scale. I found setting it to 1200/webview.width gives something similar to what I'm looking for. It prevents the page from shrinking when resizing. However, everything ends up getting very blurry, so it can't be a solution for me. I'll try digging through the experimental settings some more. It's too bad that it isn't better documented. It is so sad that this zooming "feature" can't be turned off. It looks like QWebView behaves properly by default, but it is a Qt widget, not a Qt Quick widget. So I won't be able to use it in my application. If anyone out there knows how to fix this, please help!

@mcosta Thank you so much. The example that you have provided me looks promising. I will start with that, and see how I can extend further.

Hi and welcome to devnet, Did you try with QCamera and it's friendly classes ?

@cybercatalyst You're right. Thanks for your answers anyway, it really helped me. ;)

Hi @LuisEnrique, The Qt way to do it is using QString::number.