On Tuesday 10 December 2013 23:31:33 David Faure wrote:
> On Tuesday 10 December 2013 21:48:09 Dominik Haumann wrote:
> > It seems that the behavior for "None" is different. Interestingly,
> > KSaveFile also behaved like this (KFilterDev did not change after all I
> > guess).
> I'm surprised, becau
On Tuesday 10 December 2013 23:31:33 David Faure wrote:
> On Tuesday 10 December 2013 21:48:09 Dominik Haumann wrote:
> > However, here it comes: Changing
> > -KCompressionDevice device(&file, false,
> > KCompressionDevice::GZip);
> > +KCompressionDevice device(&file, false,
> > KCo
On Tuesday 10 December 2013 21:48:09 Dominik Haumann wrote:
> However, here it comes: Changing
> -KCompressionDevice device(&file, false, KCompressionDevice::GZip);
> +KCompressionDevice device(&file, false, KCompressionDevice::None);
> will run into this issue.
Great. A unittest p
Hi David,
On Wednesday 04 December 2013 14:42:19 David Faure wrote:
> On Monday 02 December 2013 22:31:43 Dominik Haumann wrote:
> > Hi,
> >
> > porting KSaveFile to QSaveFile, I stumbled into the following:
> >
> > // This method has been made private so that it cannot be called,
> > // in orde
On Monday 02 December 2013 22:31:43 Dominik Haumann wrote:
> Hi,
>
> porting KSaveFile to QSaveFile, I stumbled into the following:
>
> // This method has been made private so that it cannot be called,
> // in order to prevent mistakes.
> void QSaveFile::close()
> {
> qFatal("QSaveFile::close
On Mon, Dec 2, 2013 at 10:31 PM, Dominik Haumann wrote:
> Hi,
>
> porting KSaveFile to QSaveFile, I stumbled into the following:
>
> // This method has been made private so that it cannot be called,
> // in order to prevent mistakes.
> void QSaveFile::close()
> {
> qFatal("QSaveFile::close ca
Hi,
porting KSaveFile to QSaveFile, I stumbled into the following:
// This method has been made private so that it cannot be called,
// in order to prevent mistakes.
void QSaveFile::close()
{
qFatal("QSaveFile::close called");
}
In Kate, we use a QSaveFile saveFile(...); and then use
KCom
