Thanks for your mail..Yes did try with valgrind but couldn't detect memory
issue may be due to the way our app is designed using threading.
But wondering why it throws segmentation fault if qApp instance is created
on stack but not on Heap as I understand that it is mandatory to construct
qApp
For one of my projects I had to "fork" QQuickTextNode,
QQuickTextNodeEngine and QQuickTextDocument to make sure I can implement
or fix needed behavior
On 12/17/18 5:44 PM, Fabrice Salvaire wrote:
Dear Qt users,
Is there people around who needed to hack QQuickTextNode private API ?
IMHO it
On Monday, 17 December 2018 10:27:37 PST René J. V. Bertin wrote:
> I don't know about secure deletion but the compression in NTFS and btrfs (or
> ZFS) is not a property you request when you open a file AFAIK. It's a
> filesystem property that is set at the level of the directory or dataset.
> HFS
On Monday December 17 2018 22:35:23 Konstantin Tokarev wrote:
> I'm not sure about ZFS, but other mentioned file systems support per-file
> compression
> setting. In Linux this is done by setting FS_COMPR_FL flag in FS_IOC_GETFLAGS
> ioctl
Interesting, I didn't know about this. It certainly
17.12.2018, 22:28, "René J. V. Bertin" :
> Thiago Macieira wrote:
>
>> How does that work? Is that just an ioctl, fcntl or a similar system call on
>> the open file descriptor? If so, you can do it right now.
>
> Unfortunately, no. Decompression is transparent like you'd expect from a
>
> Sent: Monday, December 17, 2018 at 1:19 PM
> From: "Samuel Rødal"
> To: "Jason H"
> Cc: inter...@lists.qt-project.org
> Subject: Re: [Interest] Understanding QImage::transformed()
>
...
> Btw, I think instead of using QImage::transformed() here which is a
> bit wasteful as it generates a
Thiago Macieira wrote:
> How does that work? Is that just an ioctl, fcntl or a similar system call on
> the open file descriptor? If so, you can do it right now.
Unfortunately, no. Decompression is transparent like you'd expect from a
filesystem level for of compression, but you have to do the
On Mon, Dec 17, 2018 at 7:00 PM Ramakanth Kesireddy
wrote:
> Yes we do have Qt running in worker thread(pthread)..Does it throws
> segmentation fault if we donot wait for the thread(like pthread::join) to
> exit event loop and destroy objects accordingly?
>
Segmentation faults are not thrown,
On Mon, Dec 17, 2018 at 7:00 PM Jason H wrote:
>
> > Sent: Monday, December 17, 2018 at 10:06 AM
> > From: "Jason H"
> > To: "Samuel Rødal"
> > Cc: inter...@lists.qt-project.org
> > Subject: Re: [Interest] Understanding QImage::transformed()
> ...
> >
> > Thanks Samuel, I was confused by this
17.12.2018, 20:13, "Thiago Macieira" :
> On Monday, 17 December 2018 01:36:50 PST René J.V. Bertin wrote:
>> Using HFS compression can be very beneficial for files that you write once
>> and read often (or very infrequently) as well as for tiny files (which are
>> reduced to only a directory
On Monday, 17 December 2018 02:43:36 PST Ramakanth Kesireddy wrote:
> Why does the QApplication instance throw seg fault when created on stack?
Because there's a bug somewhere. It's likely the problem is in your code. I
recommend trying to valgrind your application and/or reducing it until you
Souds like they are getting a Promise result from the framework and are not
"await"ing for it.
> Sent: Saturday, December 15, 2018 at 3:35 PM
> From: "Roland Hughes"
> To: "Jason H"
> Cc: interest@qt-project.org
> Subject: Re: [Interest] resturn string to javascript inside QWebEngineView
>
>
+1
> On 17 Dec 2018, at 16:44, Fabrice Salvaire wrote:
>
> Dear Qt users,
>
> Is there people around who needed to hack QQuickTextNode private API ? IMHO
> it restricts strongly the possibility to develop modern custom QML items.
>
> cheers,
>
> Fabrice
>
>
>
>
> Sent: Monday, December 17, 2018 at 10:06 AM
> From: "Jason H"
> To: "Samuel Rødal"
> Cc: inter...@lists.qt-project.org
> Subject: Re: [Interest] Understanding QImage::transformed()
...
>
> Thanks Samuel, I was confused by this part for transformed(): "The
> transformation matrix is
Yes we do have Qt running in worker thread(pthread)..Does it throws
segmentation fault if we donot wait for the thread(like pthread::join) to
exit event loop and destroy objects accordingly?
On Mon, 17 Dec, 2018, 17:00 Konstantin Shegunov On Mon, Dec 17, 2018 at 1:26 PM Andrew Ialacci wrote:
>
On Monday, 17 December 2018 01:36:50 PST René J.V. Bertin wrote:
> Using HFS compression can be very beneficial for files that you write once
> and read often (or very infrequently) as well as for tiny files (which are
> reduced to only a directory entry). Being able to create such files
>
Dear Qt users,
Is there people around who needed to hack QQuickTextNode private API ?
IMHO it restricts strongly the possibility to develop modern custom QML
items.
cheers,
Fabrice
___
Interest mailing list
Interest@qt-project.org
> Sent: Saturday, December 15, 2018 at 10:32 AM
> From: "Samuel Rødal"
> To: "Jason H"
> Cc: inter...@lists.qt-project.org
> Subject: Re: [Interest] Understanding QImage::transformed()
>
> Accidentally replied off-list, replying again here.
>
> On Fri, Dec 14, 2018 at 11:56 PM Jason H wrote:
Rene',
Cannot answer your question, but, I'm a bit curious about "how a file
system supports it?" Not trying to be a jerk, just seeking a bit of
comprehension because I know how we do this in other worlds. In the
OpenVMS world we have FDL (File Definition Language) and C/C++ language
+1
Am 17.12.18 um 12:44 schrieb Frank Hemer:
+1
On Monday, 17 December 2018 08:11:34 CET Amr Kamal wrote:
Hello,
when Downloading the last version of QT 5.12.0 it only provides MinGW 64bit
for windows which makes some problem with previous projects that used
32bit version especially if
On Mon, Dec 17, 2018 at 1:39 PM Andrew Ialacci wrote:
> Assuming each threads quit() is called and all operations are stopped in
> each thread correctly is using a loop and sleep still ok?
>
Ok's a relative term, but I wouldn't do (or recommend) it. That's the whole
reason you have
+1
On Monday, 17 December 2018 08:11:34 CET Amr Kamal wrote:
> Hello,
>
> when Downloading the last version of QT 5.12.0 it only provides MinGW 64bit
> for windows which makes some problem with previous projects that used
> 32bit version especially if there is any kind of third-party library,
Wow, Yes!
I forgot to include actually killing the threads first before checking if they
are running. Oops…
Assuming each threads quit() is called and all operations are stopped in each
thread correctly is using a loop and sleep still ok?
From: Konstantin Shegunov
Date: Monday, December
On Mon, Dec 17, 2018 at 1:26 PM Andrew Ialacci wrote:
> I’ve had this issue on Windows especially when destroying worker threads
> on an application exit.
>
Which you shouldn't do.
What I ended up doing was sleeping the main thread until each worker
> threads isRunning() return false;
>
> I’d
I’ve had this issue on Windows especially when destroying worker threads on an
application exit.
What I ended up doing was sleeping the main thread until each worker threads
isRunning() return false;
Something like:
http://share.dkai.dk/Screen-Shot-2018-12-17-12-01-50-n9RsDe43KW.png
I’d love
Hi,
I'm using Qt 4.8 on TI Sitara embedded linux.
Firstly, a segmentation fault occurs in the destructors, which are called
after the event loop is exited. Trying to find the root cause for this.
However, if we comment out the mainwidget destructor call, the QApplication
instance created on
Hi,
Is anyone aware of a QFile subclass (or comparable) that writes data using HFS
compression if the filesystem supports it (HFS+ and APFS)?
If not, and that's more of a question for the development ML: has thought ever
been given to make this an option in the QFile class itself?
Using HFS
27 matches
Mail list logo
