Am 14.09.2012 um 18:50 schrieb Till Oliver Knoll :
> ...
> In other words: DON'T reply to Digest messages - it's mostly useless! People
> can only *guess* to what you're actually referring to (especially if you omit
> any quotation!).
Refer and reply to this thread instead: "Access Violation u
Am 14.09.2012 um 17:29 schrieb Rayner :
> If you want to keep file as a non member pointer in your ctor, then you must
> set a parent to avoid memory leaks:
Likewise, if you want to reply to a certain topic, you should make sure to set
"a valid email parent" to you reply, as to avoid informati
If you want to keep file as a non member pointer in your ctor, then you must
set a parent to avoid memory leaks:
QFile *file = new QFile(this);
By setting a parent, memory taken by the file pointer also is destroyed on its
parent deletion
10mo. ANIVERSARIO DE LA CREACION DE LA UNIVERSIDAD DE LAS
Now you're leaking memory every time that function is called.
On 14/09/12 15:42, Heidler, Kirstin (GE Oil & Gas) wrote:
> Hi,
>
> thank you, I also found a different solution. I am not sure why it is
> working, but it does.
> I simply create the file object as a pointer to the file object like
Op 14-9-2012 14:42, Heidler, Kirstin (GE Oil & Gas) schreef:
> Hi,
>
> thank you, I also found a different solution. I am not sure why it is
> working, but it does.
> I simply create the file object as a pointer to the file object like that:
> QFile *file;
> file = new QFile(fileName);
>
Hi,
thank you, I also found a different solution. I am not sure why it is working,
but it does.
I simply create the file object as a pointer to the file object like that:
QFile *file;
file = new QFile(fileName);
file->open(QIODevice::ReadOnly);
Thank you for the hint. :)
Kirstin
---
I guest "file" may be available only in ctor scope, try to make "file" a member
of FileParser
10mo. ANIVERSARIO DE LA CREACION DE LA UNIVERSIDAD DE LAS CIENCIAS
INFORMATICAS...
CONECTADOS AL FUTURO, CONECTADOS A LA REVOLUCION
http://www.uci.cu
http://www.facebook.com/universidad.uci
http://www.
Hi,
In the FileParser constructor, you create a QFile object on the stack. This
means that the QFile object will get destroyed when the constructor is done.
Then you create a QTextStream and pass that a pointer to the QFile. This
pointer will however point to invalid memory after the constructor
Here is what I do:
I open a File with QFile. Next I create a QTextStream for that file. This
TextStream is saved in a member to my FileParsing-class.
While still in the constructor everything works fine. I can access the
TextStream, print it's device's size etc.
The problem arises once my Test
Yes I've seen all of these problems too and they've been present since Qt 4.6
(a bad release which introduced numerous regressions on OSX).
QDesigner is full of glitches and is in need of some attention; the one where
the control panel controls 'float' above the panel comes to mind.
The QPushBu
10 matches
Mail list logo
