|
|
@ -256,7 +256,7 @@ class. To overload the "<<" you would e.g. do something like this:
|
|
|
|
QDataStream& operator<<(QDataStream& stream, MyData& data)
|
|
|
|
QDataStream& operator<<(QDataStream& stream, MyData& data)
|
|
|
|
{
|
|
|
|
{
|
|
|
|
int type = data.type;
|
|
|
|
int type = data.type;
|
|
|
|
QString name = data.name;
|
|
|
|
TQString name = data.name;
|
|
|
|
stream << type << name;
|
|
|
|
stream << type << name;
|
|
|
|
return stream;
|
|
|
|
return stream;
|
|
|
|
}
|
|
|
|
}
|
|
|
@ -374,7 +374,7 @@ the memory of the names in a release version.
|
|
|
|
For as long as you use standard types for your properties (int, long, bool,
|
|
|
|
For as long as you use standard types for your properties (int, long, bool,
|
|
|
|
...) you should always be able to see the value of the property. If you just see
|
|
|
|
...) you should always be able to see the value of the property. If you just see
|
|
|
|
"unknown" then this type has not been implemented. You can connect to the signal
|
|
|
|
"unknown" then this type has not been implemented. You can connect to the signal
|
|
|
|
KGamePropertyHandler::signalRequestValue() and supply a QString with the value
|
|
|
|
KGamePropertyHandler::signalRequestValue() and supply a TQString with the value
|
|
|
|
yourself. If you do so for a standard type please also submit a bug report!
|
|
|
|
yourself. If you do so for a standard type please also submit a bug report!
|
|
|
|
|
|
|
|
|
|
|
|
Currently the dialog does *not* update automatically! So you alway have to click
|
|
|
|
Currently the dialog does *not* update automatically! So you alway have to click
|
|
|
|