[SOLVED] QLabel won't update pixmap from inside function

[Tymer]

My main.cpp:

#include "widget.h"
#include "widget1.h"
#include <QApplication>

int main(int argc, char *argv[])
{
    QApplication a(argc, argv);

    Widget w;
    widget1 w1;
    w1.show();
    w.show();


    return a.exec();
}

[SGaist]

Ok, you are not showing the widget you have connected. Your Widget w in your main.cpp is not the same as the one you have instantiated in your widgte1 constructor.

[Tymer]

So I should make my widget a singleton, more or less? How would I go about that?

[SGaist]

No, not at all. Either:

1. Remove the widget from MainWindow and connect the one in main.cpp
2. Remove the one from main.cpp and show the one from MainWindow

[Tymer]

How would I connect to the instance in main?

[SGaist]

By using the static version of QObject::connect

[Tymer]

I know this is really basic, but I'm having a bit of a brain fart. I want to make a pointer to the instance I create in main, but I don't want my class to know too much about what's going on in main. How do I do this so that I can create a connection to the object in main from a different widget?

[Tymer]

Right now I have:

main.cpp

myWidget* w = new myWidget;
actionTestWindow* t = new actionTestWindow(w, new QWidget);

actionTestWindow.cpp

actionTestWindow::actionTestWindow(myWidget* Widget, QWidget *parent) :
    QWidget(parent),
    ui(new Ui::actionTestWindow)
    {
        ui->setupUi(this);

        Widget = new myWidget;

The actionTestWindow is no longer showing, and I think it has something to do with how I insert the QWidget parameter.

[SGaist]

Roll back to before you modified that constructor. Just call '''Widget->show();'''

[Tymer]

Alright, finally got this problem SOLVED!

I pass in an instance of myWidget as a parameter of actionTestWindow in main. It's important to note that you need to specify the QWidget as parent = 0 or it will not show. The relevant code looks something like this:

main.cpp

QWidget* parent = new QWidget;
parent = 0;
myWidget* w = new myWidget;
actionTestWindow* a = new actionTestWindow(w,parent);

w->show();
a->show();

actionTestWindow.h

class actionTestWindow : public QWidget {
myWidget* m;

public:
actionTestWindow(myWidget* mW, QWidget* parent = 0);

actionTestWindow.cpp

actionTestWindow::actionTestWindow(myWidget* mW, QWidget* parent)
{
this->m = mW;
/*use this->m to reference myWidget*/
}

**note: irrelevant or standard code was mostly emitted.

[SGaist]

And there you have a memory leak.

Why don't you just show the myWidget you had originally created in Widget ?

[Tymer]

@SGaist It's a pretty complicated project. The actionTestWindow is pretty much just what it sounds like...A test window. The point is to make sure that I can successfully pass the signals I need and get the reactions I need for when I connect it to a more complicated process. myWidget needs to be shown from main as soon as the program starts running. Having it wait to show until the process that it displays info from runs would be a problem. The code will be passed around to many other people to be changed for future projects, and we're trying to avoid making them dig through code to find things as much as possible. It needs to be easy to just change a class slightly and change the instantiation slightly in order to make a change.

Can you point out the exact memory leak? I was under the impression that you can pass in instances of classes as parameters. It's a pretty common thing to do in Java, and I've at least heard of it being done in C++. There is a lot of code omitted. Destructors, importantly.

[SGaist]

You have

QWidget* parent = new QWidget;
parent = 0; << the original parent is now lost and not destroyed
myWidget* w = new myWidget;

Since it needs to be the first widget, then create it in main. Connect your MainWindow to it also in main.

You should rather avoid making that test widget known to any and every widget of your software. Doing so you'll avoid tight coupling and maintenance hell.

[Tymer]

Changed it to QWidget* parent = 0;. No more memory leak, everything works as expected.