List Info

Thread: const QVariant& localOrRepoLocationSrc




const QVariant& localOrRepoLocationSrc
user name
2007-06-06 11:21:15
some methods such as diff() and merge() takes QVariant as a
local or repository location. When the value is QString, no
problem.
What matter is case of KUrl, since there is no native
QVariant-api
to handle KUrl.

I think this one is candidate.
QVariant qVariantFromValue ( const T & value )

And we should allocate unique UserType, which is returned
by
QVariant::userType().

Any comment?, if none I'll docuemt and define new enum for
KUrl

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

Re: const QVariant& localOrRepoLocationSrc
user name
2007-06-06 11:50:18
On 06.06.07 12:21:15, dukju ahn wrote:
> some methods such as diff() and merge() takes QVariant
as a
> local or repository location. When the value is
QString, no problem.
> What matter is case of KUrl, since there is no native
QVariant-api
> to handle KUrl.
> 
> I think this one is candidate.
> QVariant qVariantFromValue ( const T & value )
> 
> And we should allocate unique UserType, which is
returned by
> QVariant::userType().
> 
> Any comment?, if none I'll docuemt and define new enum
for KUrl

All that is already done in KUrl itself, we don't need to do
that. IIRC
you can just do

QVariant( someUrl );

And later on do

KUrl myurl = variant.value(); (or value<KUrl>, not
sure).

Andreas

-- 
Don't hate yourself in the morning -- sleep till noon.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )