Access the UI, from multiple windows.

Loc888

@mrjj I create it with pointer already, i mean the object.
I dont know how to use signal and slots in this example, what and wher should i type to pass the object??
I use it with timers, but not with Windows objects.

mrjj

Hi
With signals and slots your would pass the data not the objects.
Normally you hook things up in mainwindow as it knows most other class.
But really depends on where its created etc.

Loc888

@mrjj Sorry, but i rly dont understand... I can pass the object here

void MainWindow :: GetWindowData(Settings_Window* S_Window_Temp)   
 {

     S_Window_Temp =  & S_Window;

}

So why i cant make a reference to it from another window, if i have the access to pass it??

mrjj

@Loc888
Hi
Im not sure what part is causing your problems.
Maybe we talk about different things.

Yes, you can make a reference to a window.
or give a pointer / ref to a window to another window.

Like create settings_win in main.cpp
give it to mainwindow.
Mainwindow create a new Window and give settings_win to that also.

Loc888

@mrjj Yes, and that's the problem. Maybe i name this topic title a little bit bad, but i dont have any problem with access, because i can access them all.

The problem is, when i pass the window with that function, it's seems like another copy, not reference, so when i change something, nothing happens because it change the copy variables, and i dont know why it happend.

If i pass ther the window object, UI stuff should be ther??

jsulm

@Loc888 Let's clean up your code.

// You need to declare S_Window_Temp as reference to pointer, else you cannot change it inside GetWindowData!
void MainWindow :: GetWindowData(Settings_Window* &S_Window_Temp)   //<< Here i send Object from Settings_Window created in Window1
{  
 S_Window_Temp =  &S_Window; 

 //  So i expect C (Object form Window1)  should be equal to S_Window (Object form MainWindow ), but it's not.
}

Actually you should simply return the pointer from GetWindowData as your current API design is bad (it isn't a good idea to change method parameters from inside the method):

Settings_Window* void MainWindow :: GetWindowData()
{  
    return &S_Window; 
}

Loc888

@jsulm If i just copy and paste, your code, it gives me an error.

The best solution I found is just create the definition of the object in mainwindow.cpp under include, i test it with my own class, and it works exacly how i wanted it.

Unfortunately when i do the same thing with the Window, it crash the application and gives a message:

"QWidget: Must construct a QApplication before a QWidget"

Any way to fix it?

SGaist

Hi,

The usual fix to this one is: don't create static QWidget based objects.

Loc888

@SGaist I dont know what you mean.

mrjj

@Loc888
Hi
You cannot have global Widgets as they are NOT
allow to be constructed before QApplication in main.
They must be pointers and you can first new them After application is created.

SGaist

If you have anything that looks like static MyClass thingy where MyClass is derived from QWidget, then remove it.

Loc888

@mrjj I tried by reference, and this happend:

Error: 'QWidget& QWidget::operator=(const QWidget&)' is private
Class &operator=(const Class &) Q_DECL_EQ_DELETE;
^

mingw48_32\include\QtWidgets\qwidget.h:728: in expansion of macro 'Q_DISABLE_COPY'
Q_DISABLE_COPY(QWidget)
^

It happend in this line Class &operator=(const Class &) Q_DECL_EQ_DELETE;

I try later with pointers, and will see what happend.

SGaist

For more information why, read this.

Loc888

@SGaist

Now i tried with pointers, error :

error: invalid operands of types 'Settings_Window*' and 'Settings_Window*' to binary 'operator*'
A* &Settings_Widget;
^

void MainWindow::Get_Window_Data(Settings_Window* A)
{

A* &Settings_Widget;

}

What i did wrong?

mrjj

@Loc888
Hi
Why not just
Settings_Window* MainWindow::Get_Window_Data()
{
return Settings_Widget; // Settings_Widget is * (pointer) ?
}

Loc888

@mrjj

It run at least, but is not working. If i check something, then press the button with this code, nothing happened. Probably is another copy.
I am tired, tomorrow i try something else.

Is this the way how i should use it?

MainWindow B;


if(B.Get_Window_Data()->ui->Checker_Box_01->isChecked())
{

    //Do something

}

mrjj

Hi
Yes but im old school and always check pointers
so i would do

MainWindow B; // this should not be a second instance but the one you (might) create in main.cpp

Settings_Window * win=B.Get_Window_Data();

if (!win) {
qDebug() << "NULL ptr from Get_Window_Data";
return;
}
if(win->ui->Checker_Box_01->isChecked())
{
    //Do something
}
if(win->ui->Checker_Box_XX->isChecked())
{
    //Do something
}

However, the UI variable is private so unless the using class is friend, its not allowed.
So you make make UI public ( bad design )
or provide access functions for the widgets.

jsulm

@Loc888 said in Access the UI, from multiple windows.:

B.Get_Window_Data()->ui->Checker_Box_01->isChecked()

From software design point of view this is so bad!
You should not expose internal details of your MainWindow like that.
Add public methods to MainWindow which return needed invormation without exposing internal implementation details.
Example:

class MainWindow...
{
public:
    bool isSomethingActivated()
    {
        return ui->Checker_Box_01->isChecked();
    }
}

MainWindow B;
if(B.isSomethingActivated())
{
    //Do something
}

Now, the user of MainWindow does not have to know anything about how the MainWindow is designed (what UI elements it has for example) - it just calls a public interface method to get the information. Usn't this much nicer? One more advantage of this approach: if you later change your MainWindow UI the caller of the MainWindow will not be affected.
Example:

class MainWindow...
{
public:
    bool isSomethingActivated()
    {
        // You decided that the condition should be different
        return ui->Checker_Box_01->isChecked() && ui->Checker_Box_02->isChecked();
    }
}

// No need to change the caller of MainWindow
MainWindow B;
if(B.isSomethingActivated())
{
    //Do something
}

mrjj

@jsulm
And we come full circle \o/
I told OP that 4 days ago, but he seems unwilling to
create access functions :)
Maybe seeing your good example, OP will feel the joy of good design
and do it the right way.

Loc888

@mrjj

It makes me a little bit mad, why everything need's to be complicated.
So, in main window can i use something like that:

  B.Get_Window_Data()->ui->Checker_Box_01->isChecked()

But in other window, i need to do it in other way?