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

List:       kde-devel
Subject:    Re: How to debug kioslave problems ? [Was: Problem opening
From:       David Faure <faure () kde ! org>
Date:       2006-04-03 20:43:08
Message-ID: 200604032243.09989.faure () kde ! org
[Download RAW message or body]

On Monday 03 April 2006 21:41, Pavel Troller wrote:
>   What to do next ? Is it necessary to write a real get(), or could it be
> possible to omit its call for kio_bluetooth, as it used to be ?

I'm guessing that it implements copy()? And it has copyToFile=true in the .protocol?
And that you used to copy to file:/ previously, but nowadays you're copying to other 
protocols instead, like system:/ or media:/ ?
This would explain it. Otherwise my crystal ball is deficient ;)

To explain this: get() is used to read a file, except when the slave implements copy()
and we're copying to file:/, then instead of shipping the data back to the app, the slave
is in charge of directly writing it out into a file. So get isn't called in that case.
But in most other cases - copying to other protocols, or if copy() isn't implemented,
then get() is the -only- way to get the data. Sounds to me like it should be implemented...
or is bluetooth:/ not about reading files somehow?

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).

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

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