QAbstractListModel data to QML TableView why not shown through QQmlApplicationEngine

[kiwimess]

It is not about QQmlApplicationEngine. Nor anything between TableView and QAbstractListModel. I made a simple test with Animal example and it showed everything ok.

So the problem must be in that I have many models. Or models are not ready somehow when qml loaded and the ListView gets updated afterwards and TableView isn't.

[anda_skoa]

You are not exporting rokmodel as an object but as a value. Are you sure you want to do that?

Btw, since you also export "this" as "product", why do those hacky connects at the end? Would be better to just handle the signals in QML.

Cheers,
_

[kiwimess]

I was just coming to tell that this was really a rookie mistake. Of course the data vanished in the end of constructor because of this: ComboModel combo; Changed it to pointer -> problem solved.

anda_skoa, do you mean using js in QML to handle signals? I'm having this Q_PROPERTY(QString sum READ sum WRITE setSum NOTIFY sumChanged) in my class and I change the product.sum value in QML from the class. I try to use only C++ and no js in this project.

Thanks for the help Anda.

[anda_skoa]

I meant something like this:

onListSignal: product.listSignal(nameOfSignalArgument)

onListSignal: product.listSignal(nameOfSignalArgument)

To copy to clipboard, switch view to plain text mode 

I.e. using the QML signal handler and calling the C++ object's slot.

That way you don't need to make any assumptions in C++ on what the QML scene looks like (currently it assumes that the first object has those signals).

Cheers,
_

[kiwimess]

Ok, I am doing just that to find out which line clicked:

onClicked: applicationWindow.listSignal(tableView.currentRow)

onClicked: applicationWindow.listSignal(tableView.currentRow)

To copy to clipboard, switch view to plain text mode 

Product is different. It is meant to change the sum text in QML from C++.

[anda_skoa]

I see.

Then you could just do

onClicked: product.listSignal(tableView.currentRow)

onClicked: product.listSignal(tableView.currentRow)

To copy to clipboard, switch view to plain text mode 

i.e. calling the slot "listSignal" on object "product" directly.

Cheers,
_

[kiwimess]

I have one more question to you, if you like to help a bit more...

When I run this in my testprogram main, it shows line data ok.

LineModel model;
 
model.addLine(Line("Candy", "Ben", "10"));
model.addLine(Line("Paper", "Ben", "20"));
model.addLine(Line("Matches", "Ben", "30"));
 
QQmlApplicationEngine *engine = new QQmlApplicationEngine;
QQmlContext *ctxt = engine->rootContext();
ctxt->setContextProperty("myModel", &model);
engine->load(QUrl(QStringLiteral("qrc:/main.qml")));
 
Line line = model.get(1);
qDebug() << line.article();
qDebug() << line.person();
qDebug() << line.price();

LineModel model;

model.addLine(Line("Candy", "Ben", "10"));
model.addLine(Line("Paper", "Ben", "20"));
model.addLine(Line("Matches", "Ben", "30"));

QQmlApplicationEngine *engine = new QQmlApplicationEngine;
QQmlContext *ctxt = engine->rootContext();
ctxt->setContextProperty("myModel", &model);
engine->load(QUrl(QStringLiteral("qrc:/main.qml")));

Line line = model.get(1);
qDebug() << line.article();
qDebug() << line.person();
qDebug() << line.price();

To copy to clipboard, switch view to plain text mode 

But when I run it from in my another programs class where linemodel is (now) member value (I hope this is said right).
Now the program crashes, when run this function.

.h:
LineModel *linemodel;
Line *oneline;
 
class:
//Line *oneline = new Line;
Line oneline = linemodel->get(1);
qDebug() << oneline.article();

.h:
LineModel *linemodel;
Line *oneline;

class:
//Line *oneline = new Line;
Line oneline = linemodel->get(1);
qDebug() << oneline.article();

To copy to clipboard, switch view to plain text mode 

And the get, which is the same in working and not working programs.

Line LineModel::get(int index) const 
{
    const Line line = m_lines[index];
    return line;
}

Line LineModel::get(int index) const 
{
    const Line line = m_lines[index];
    return line;
}

To copy to clipboard, switch view to plain text mode 

[anda_skoa]

is the linemodel pointer valid?
Is the index valid?

Cheers,
_

[kiwimess]

h:
private: Linemodel *linemodel; Line *oneline;
 
constructor:
LineModel *linemodel = new LineModel;
linemodel->addLine(Line("Book", "1,40", "Heidi"));
linemodel->addLine(Line("Paper", "2,40", "Heidi"));
linemodel->addLine(Line("Pen", "12,40", "Heidi"));

h:
private: Linemodel *linemodel; Line *oneline;

constructor:
LineModel *linemodel = new LineModel;
linemodel->addLine(Line("Book", "1,40", "Heidi"));
linemodel->addLine(Line("Paper", "2,40", "Heidi"));
linemodel->addLine(Line("Pen", "12,40", "Heidi"));

To copy to clipboard, switch view to plain text mode 

And here in beginning of line 1. debugger says that "linemodel not accessible". Doesn't the *linemodel in constructor hold the data? And the private members are available to everywhere inside that class? This is inside a slot (shouldn't make any difference?)

Line oneline = linemodel->get(0);
qDebug() << oneline.article();

Line oneline = linemodel->get(0);
qDebug() << oneline.article();

To copy to clipboard, switch view to plain text mode 

[anda_skoa]

[QUOTE=kiwimess;281990]

constructor:
LineModel *linemodel = new LineModel;

constructor:
LineModel *linemodel = new LineModel;

To copy to clipboard, switch view to plain text mode 

If you really have that in your constructor then you have the "linemodel" member uninitialized.

And the private members are available to everywhere inside that class?

Yes.
But if you code above is actually what you have, then you are not accessing the member but shadowing it with a local variable.

Cheers,
_

[kiwimess]

So now when I have LineModel *linemodel in header as private member, I need to make a function to pass it as reference to be used in main. And this way all the data is usable in this class later? Sorry for simple questions, I'm simple person

[anda_skoa]

As a pointer, since you need a pointer to export it as a context property.

But you better post updated code, otherwise we might be talking about very different things.

Cheers,
_