[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Making types visible to KConfig
From:       Thomas Braxton <kde.braxton () gmail ! com>
Date:       2009-01-31 1:45:17
Message-ID: 928c3f1b0901301745x6584b796yfada21804afeaec () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


But remember using a list is how at least half of the types in KConfig are
handled internally. So converting a type that Qt doesn't know about and all
the data is of the same type, the simplest way is to use a list and
everything else is handled for you. Sorry about the top post, I don't have a
choice at the moment :(

On Jan 30, 2009 6:17 PM, "Oswald Buddenhagen" <ossi@kde.org> wrote:

On Fri, Jan 30, 2009 at 05:40:40PM -0600, Thomas Braxton wrote: > On Jan 30,
2009 4:39 PM, "Oswald B...

> > anyway, you'll have to convert yourself and pass the values as > >
strings (QByteArray is more e...

> Actually the easiest way would probably be to pass the values as >
QList<qreal> to/from KConfig an...
well, yes, for *that* data type it would work. it might make a generic
approach even harder, though. note also that constructing a list is more
expensive than just serializing directly to a string.
in any case it is manual conversion ...

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
<<

[Attachment #5 (text/html)]

<p>But remember using a list is how at least half of the types in KConfig are handled internally. So \
converting a type that Qt doesn&#39;t know about and all the data is of the same type, the simplest way \
is to use a list and everything else is handled for you. Sorry about the top post, I don&#39;t have a \
choice at the moment :(</p>

<p><blockquote>On Jan 30, 2009 6:17 PM, &quot;Oswald Buddenhagen&quot; &lt;<a \
href="mailto:ossi@kde.org">ossi@kde.org</a>&gt; wrote:<br><br><p><font color="#500050">On Fri, Jan 30, \
2009 at 05:40:40PM -0600, Thomas Braxton wrote: &gt; On Jan 30, 2009 4:39 PM, &quot;Oswald \
B...</font></p><p><font color="#500050">&gt; &gt; anyway, you&#39;ll have to convert yourself and pass \
the values as &gt; &gt; strings (QByteArray is more e...</font></p><p><font color="#500050">&gt; Actually \
the easiest way would probably be to pass the values as &gt; QList&lt;qreal&gt; to/from KConfig \
an...</font></p>well, yes, for *that* data type it would work. it might make a generic<br> approach even \
harder, though. note also that constructing a list is more<br> expensive than just serializing directly \
to a string.<br> in any case it is manual conversion ...<br>
<p><font color="#500050"> 
&gt;&gt; Visit <a href="http://mail.kde.org/mailman/listinfo/kde-devel#unsub">http://mail.kde.org/mailman/listinfo/kde-devel#unsub</a> \
to unsubscribe &lt;&lt; </font></p></blockquote></p>



>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]