Problem reading an Xml file with QXmlStreamReader
-
I changed my code.
It doesnt matter that the program will find twice the tag patient_id.
The problem is that in the xml file are the same tags (from examinations to /examinations) many times, and i tried to debug my code and i saw that my code reads the xml (from examinatios to /examinations) only once. it "thinks" that it is the end of the file but it isnt ( it has more tags).@
while(!xml.atEnd() && !xml.hasError()){
if (xml.name() == "patient_id") {
id2=xml.readElementText();
if (itemId==id2)
flag=1;
}
xml.readNext();
}
@ -
Hi,
I have created some checkboxes with some examinations.
@checkbox1 = new QCheckBox("Geniki Aimatos", this);
checkbox2 = new QCheckBox("UREA", this);
checkbox3 = new QCheckBox("CREA", this);@but i want to change my code and read the examinations from an xml file. the xml may change in the future.It may be bigger.
So how can i create the checkboxes? each checkbox should have a different name. if i count the examinations of the file, how can i define the checkboxes?2 replies
November 7, 2011
Lukas Geyer Lukas Geyer
Gene Splicer
736 postsGroupie L1 |reportUse QXmlStreamReader to read the XML, create QCheckBoxes on the fly and add them to a layout, for example a QVBoxLayout to have them aligned properly. Use setObjectName() to associate a unique identifier with each checkbox.
I did what you said (Lucas), but can you explain me how to use the setObjectName() please?
i can't find any documentation.my code is :
QCheckBox* checkbox1=new QCheckBox();
@File* file = new QFile("c:/exetaseis.xml");
if (!file->open(QIODevice::ReadOnly | QIODevice::Text)) {
QMessageBox::critical(this,
"QXSRExample::ok",
"Couldn't open exetaseis.xml",
QMessageBox::Ok);
return;
}QXmlStreamReader xml(file);
while (!xml.atEnd() && !xml.hasError()) {
if(xml.tokenType() == QXmlStreamReader::StartElement)
if (xml.name() == "lab_test"){
arithmos_exetasewn++;
checkbox1->setObjectName("check");
}
}xml.readNext();
_layout2->addWidget(checkbox1);
@Is the way I used the setobjectname correct? and then i should use sth like this
@QList<QCheckBox *> allCheckboxes=checkbox1->findChildren<QCheckBox *>();
@ -
[quote author="annatz" date="1320921838"]
I did what you said (Lucas), but can you explain me how to use the setObjectName() please?
i can't find any documentation.
[/quote]Then you did not search properly. Here "it is":http://doc.qt.nokia.com/4.7/qobject.html#objectName-prop
Just as a side note: Use Qt Assistant (it's installed with every Qt) for searching the docs. And you did spot the DOC tab here on DevNet already, didn't you? It has a search function too.
-
You most probably want to set an unique name for your objects; checkbox1->setObjectName(QString("check") + arithmos_exetasewn) instead of checkbox1->setObjectName("check"). As every QObject can be seen as an unique entity (one reason why there is no copy ctor for QObject) there shouldn't be two QObjects having the same objectName (at least not in the same "relationship tree").
findChild() and findChildren() returns children of the invoking object. checkbox1 does not have any children. To find all checkboxes use layout2->findChildren<QCheckBox*>(), to find a specific checkbox use layout2->findChild<QCheckBox*>("checkboxN") where N is the number of checkbox you are looking for.
In addition, xml.readNext() is outside of your while - you will end up in a infinite loop.
-
I am trying to understand your requirements - again.
You want to create a series of checkboxes based on the contents of an XML file (or of a part of such a file, not very clear), and I will assume you will want to write back the settings afterwards. Right?I think you were already told in the past more than once, that you should create an in-memory representation of your data tree, as you can not read and write back small parts of it. You will need to write the whole file in one go, and thus you need all information that needs to go into the file in memory.
So, if you have a decent representation of your data in memory ("data store" from now on), only then the question arrises how to build up a UI to represent that data. So, you get:
(XML) storage format ↔ Data store ↔ UI, in stead of
XML ↔ UI.That is a big difference. Try to focus on one aspect at a time. First come up with a good, usable implementation of a data store that really is able to represent all the data you need to handle in a sane way, and has a good API for the rest of your application to use. Then, implement the loading of data (XML or whatever format you fancy) from a storage medium into your application, and the saving of the data back into that storage. You might even considder using ready-to-use frameworks for that, like QtORM or Boost::serialization. The representation and manipulation of your data comes on top of that data store. It is a really basic software design pattern to think of your application as layers. A common way to separate your application into layers is Data ↔ Business ↔ UI.
Then, on your UI design issue:
If you have a list of examinations that be any length (from 0 to hundreds) that you need to present, I would not fiddle around with creating and destroying QCheckBox objects at runtime and trying to find reference to them back using the object name. That is not very strong design at all. I would use the model-view framework instead. Items in such a model can be checkable easily. So, I would create a model (QAbstractListModel-decendent?) to show a view on this aspect of your data store. The model can then just modify the data store if a checkbox is checked or unchecked in the list.Try not to take this personally, but it seems to me that you are trying to create a medical application, dealing with patient data. Is that correct? These applications are important, can can mean the difference between life and death and much suffering if they cause medial mistakes. It seems to me that you are not qualified to build such applications. It is one thing to screw up the data store of a small store or a personal addressbook or something like that, it is quite another to screw up medical records.
-
my program reads an xml file with the patients' examinations. i want to create as many checkboxes as the examinations. But the xml file might change in the future and the number of the examinations might change.
You are right, i am trying to create a medical application. it is a project for my univercity and i am trying on my own and i find it much difficult.
-
[quote author="annatz" date="1321086833"]and how can i use for example the second checkbox?
i used @_layout2->findChild<QCheckBox*>("check2");@ and then how can i add a value to that checkbox?[/quote]What does "add value" mean? You can set the checkboxes value (checked, not checked, intermediate) using QCheckBox::setCheckState(). If you want to attach some data to it (which can be retrieved later) you can use QObject::setProperty() (every widget is a QObject).
However, although it is possible to use the UI as "data store" it is - as Andre already stated - usually way better to use a distinct "data store" layer.
-
my problem wasn't how to store my data at a data store. my application will show on the screen some checkboxes with my data. how can i dynamically create those checkboxes? i did it like
@checkbox1 = new QCheckBox("Geniki Aimatos", this);
checkbox2 = new QCheckBox("UREA", this);
checkbox3 = new QCheckBox("CREA", this);
checkbox4 = new QCheckBox("LDH", this);
checkbox5 = new QCheckBox("TBIL", this);@but i dont know how to create "x" checkboxes and add them a label like "Geniki Aimatos".
-
[quote author="annatz" date="1321123713"]my problem wasn't how to store my data at a data store. my application will show on the screen some checkboxes with my data. how can i dynamically create those checkboxes? i did it like
@checkbox1 = new QCheckBox("Geniki Aimatos", this);
checkbox2 = new QCheckBox("UREA", this);
checkbox3 = new QCheckBox("CREA", this);
checkbox4 = new QCheckBox("LDH", this);
checkbox5 = new QCheckBox("TBIL", this);@but i dont know how to create "x" checkboxes and add them a label like "Geniki Aimatos".[/quote]
Loop over the data that you have extracted from the XML data. You should have put that into some decent container (QList, QMap...) beforehand.
To ease your life, you could go with a [[Doc::QStandardItemModel]] or use a [[Doc:QTreeWidget]]. That saves you the task of writing your own AQIM based item model. The latter would be - don't take it personal - a too complicated task for you.