Need to find a way to save user inputs.

["BumbleBee"]

So I am making a kind of large app,which will be used by many people.
In a seperate widget(class) I have put a tablewidget which is empty.
User can use this tool to store data and save it.

What I mean by "save", is that once some text is entered,it will be there next time the user opens the program.
Then he might edit all the fields,add/remove colums/rows etc..

The key part here is to make the fields saveable

I have no idea how to do this..maybe there is some text file,so that I save all the data there,then read from it..or something else?

Please help.

[wysota]

And how does this differ from this thread?
http://www.qtcentre.org/threads/4520...idget-for-this

["BumbleBee"]

Tables are different than lineedits.

[wysota]

Are they...?

["BumbleBee"]

Well,for the Lineedit I do: set.setValue("text1", ui->le1->text()); then ui->le1->setText(set.value("text1").toString());
While the Tablewidget doesn't have those functions( text(),setText() )..

[Zlatomir]

QTableWidget has lines and columns that can hold QTableWidgetItems which items have setText member function.

["BumbleBee"]

Well,this is what I have so far:

void Victims::save()
{
    QSettings set("vic","tims");
    set.beginGroup("setting");
 
    int grows = ui->tw->rowCount();
    int gcols = ui->tw->columnCount();
 
    for(int i = 0; i < grows ;i++)
    {
 
        for(int j = 0; j < gcols ;j++)
            {
                QTableWidgetItem* widgetItem = ui->tw->item(grows, gcols);
                tmp = widgetItem(i,j)->text();  //tmp is a string.
                if ( tmp.isEmpty() )
                break;
            }
        set.setValue("victims", tmp); //tmp will be the string that will be put into set.value(),correct?
    }
    set.endGroup();
}

void Victims::save()
{
    QSettings set("vic","tims");
    set.beginGroup("setting");

    int grows = ui->tw->rowCount();
    int gcols = ui->tw->columnCount();

    for(int i = 0; i < grows ;i++)
    {

        for(int j = 0; j < gcols ;j++)
            {
                QTableWidgetItem* widgetItem = ui->tw->item(grows, gcols);
                tmp = widgetItem(i,j)->text();  //tmp is a string.
                if ( tmp.isEmpty() )
                break;
            }
        set.setValue("victims", tmp); //tmp will be the string that will be put into set.value(),correct?
    }
    set.endGroup();
}

To copy to clipboard, switch view to plain text mode 

However it gives me an error: widgetItem cannot be used as a function :/
Am I on the right way?

[Zlatomir]

widgetItem is already a pointer to the item at i,j index so use it without (i,j), just: widgetItem->setText("blabla");

LE: don't forget to check for null, because, if i remember correctly, if the indexes are out-of range that item function returns null

[wysota]

I suggest you come up with a universal solution that will work regardless of the item you want to store/restore. Provide classes or functions that will be called depending on the item/widget type you need to store and have some infrastructure that will call those classes/functions. You basically need something similar to QMainWindow::saveState() and QMainWindow::restoreState().

["BumbleBee"]

Right now I cannot put a simple table into settings,when you tell me to make a universal functionality..
I suppose I'd better do it seperatly and if I have time I will think of what u said.

So,my thought was to do this:
Loop through the rowcount() and create as many arrays of string.
Then use that nested loop(intthe code I pasted) and after each row,store the text into one array.
Then in restore,I would re-loop(the table) to put the arrays as text..
Is that ok?

[wysota]

Right now I cannot put a simple table into settings,when you tell me to make a universal functionality..

You are considering the two as different problems whereas it is the same problem, it's just a matter of having a single solution doing all you want today and all you might want tomorrow or having a tightly coupled solution which works for what you want today but will require the same amount of work for each of the things you'll want tomorrow and the day after.

["BumbleBee"]

Hmm..I can't really come up with an idea that would work for any widget.
Can you give me a hint?