Okay I might be making a bit of progress here. I'm not sure how this will turn out but it's worth a shot. First of all, in the Qt plugin, I export a function which renders the widgets:

extern "C" void RenderWidgets(PixelArray_t &pixelData, int const w, int const h) { assert( nullptr != &pixelData ); // just for debug parentWidget->setGeometry(0, 0, w, h); QPixmap pixmap( parentWidget->size() ); pixmap.fill(Qt::transparent); QPainter painter(&pixmap); parentWidget->render(&painter); painter.end(); QImage image = pixmap.toImage(); int const width = image.width(); int const height = image.height(); pixelData.resize( width, PixelArray_t::value_type(height) ); // 2D array of QColor for ( int x = 0; x < width; ++x ) { for ( int y = 0; y < height; ++y ) { pixelData[x][y] = (unsigned)image.pixel(x, y); } } }

In my main program which runs wxWidgets, I have a handler for the Paint event for the panel, implemented as follows:

void OnPaint(wxPaintEvent& event) { wxPaintDC dc(this); // Create a paint DC for the panel int const w = dc.GetSize().GetWidth (); int const h = dc.GetSize().GetHeight(); pfnRender(pixels, w, h); // Call the function exported by the Qt plugin assert( this->pixels.size() > 0 ); assert( this->pixels.front().size() > 0 ); wxBitmap bitmap(w, h); // Create a bitmap that matches the panel size wxMemoryDC memDC(bitmap); // Create a memory DC to work with the bitmap for ( int x = 0; x < w; ++x ) { for ( int y = 0; y < h; ++y ) { unsigned const pixel = pixels[x][y]; unsigned char r = (pixel >> 24) & 0xFF; unsigned char g = (pixel >> 16) & 0xFF; unsigned char b = (pixel >> 8) & 0xFF; unsigned char a = (pixel >> 0) & 0xFF; memDC.SetPen( wxPen(wxColour(r, g, b), 1) ); memDC.SetBrush(wxBrush(wxColour(r, g, b), wxSOLID)); //memDC.SetAlpha(a); memDC.DrawRectangle(x, y, 1, 1); // Draw 1x1 pixel } } dc.DrawBitmap(bitmap, 0, 0); }

I've tested this out and it works. So I'm able to display widgets.

But next . . . here's what I need to do:
In the wxWidgets main program, record mouse movements and mouse clicks, and send them to the Qt plugin. Then inside the Qt plugin, I need to take these movements and clicks and somehow send them to the widgets (even though the widgets aren't on screen in the canonical sense). Can anyone help me with this part?

Hi,

Based on the name, you are trying to access a repos that is internal to the Qt Company.

@James-Gallegos It works, Thanks

In case you want to access to file on remote system (where squishserver is running),
you should access them via functions offered by "remotesystem" object.
For more information regarding this object please refer to the following documentation.
https://doc.qt.io/squish/squish-api.html#remotesystem-object

Hey Everyone!

Let's go through some of the new courses on Qt Academy, what updates have been made, and what to look forward to moving forward!

Model View Delegate with QML

Get to grips with the Model View Delegate (MVD) pattern in QML and the Qt framework, gaining the skills to manage and display complex data effectively. Through hands-on projects, you’ll explore the relationship between Models, Views, and Delegates, using Qt’s built-in and custom components to present dynamic data in a structured format. By course end, you’ll create a functional weather app that showcases real-time data interaction, integrating live weather data into an intuitive user interface.

Basic Views in Qt Design Studio

Take your first steps and explore the basics of Qt Design Studio, learning to navigate its UI, essential tools, and various workspaces. By course end, you’ll confidently navigate the Qt Design Studio workspace, gaining familiarity with its interface and essential tool locations. This course is ideal for newcomers to Qt Design Studio with some background in design tools.

Creating Responsive Layouts in QML with LayoutItemProxy

In this course, you’ll delve into Proxy Layouts, a technique for building responsive layouts in QML. Starting with an overview of responsive design principles, you’ll explore the LayoutItemProxy Type and learn to apply it in various practical scenarios. Ideal for those eager to advance their UI development skills in QML, this course covers using Proxy Layouts to create adaptable, responsive interfaces.

This course was developed by Spyrosoft, experts in delivering successful Qt projects across industries. Published on Qt Academy with Spyrosoft’s permission, this material showcases their depth of expertise in Qt technologies, including Qt/QML, Qt 3D, and more.

Let's Get Thready! Multithreading with Qt

The course has been updated with new explanations and improved examples, to help you better understand atomic_flag and RAII. Some quiz questions and answers have been updated to reflect these changes.

How to Install Qt

Screenshots and instructions have been updated to reflect changes to the installion process.

General Polishing

We have been working on polishing the courses, updating the content and improving the overall experience with code examples, code snippets and quizzes based on your feedback!

Please make sure you leave reviews on the courses you take, as it helps us improve the content and make it more relevant to you.

More content is always in progress, we have upcoming courses on QML, Qt Design Studio, and more! We are always looking for feedback on what you would like to see, and looking for great people within the community to help us grow.

If you want to stay in touch, visit the academy homepage and sign up for the newsletter! qt.io/academy. You can view the whole catalog here too.

~ Ash

@jsulm said in To singleton or not to singleton, that is the question....:

You can put everything into namespaces, including classes. Or did I misunderstand you?

You do misunderstand. Please read again what I wrote in that question so I don't need to write out a full example again (though I will if you cannot get it). The question is about the fact that you can "wrap" the whole of your cpp file (note: asking about the .cpp not the .h) implementation inside a single namespace Foo { ..... all the body of the .cpp stuff without writing prefix Foo:: ... } instead of writing each of your functions as Foo::bar(). You have to to do the latter if it's class Foo. You can choose to do the same versus wrap in a namespace Foo { ... } if it's namespace Foo. Which do you prefer in your namespace .cpp file function definitions?

OK, to type it in: in the .cpp file (I'm not talking about the .h file) for a class Foo we write:

void Foo::bar() { ... } void Foo::baz() { ... }

We have no choice for a class. This also works if Foo is a namespace instead of a class.

For a namespace, but not for a class, we can alternatively write .cpp as:

namespace Foo { void bar() { ... } void baz() { ... } }

to drop the Foo:: prefix against each definition. Do you prefer this for namespaces, or the same Foo:: prefix way as required for classes?

忘記附上我使用的QT版本是5.15.14.

I had the same goal. I used Docker (Windows 10) and CROPS to run Debian container on Win10 to cross compile.
With a hefty machine (8-12 cores, 32 GB RAM) I am able to cross compile from Win10 to the target (Toradex Colibri) pretty easily

https://docs.yoctoproject.org/dev-manual/start.html#setting-up-to-use-cross-platforms-crops