Re: [Interest] Parsing data from serialport

Thank you Andre for the fast response. Ok than I found the problem, why the program need so much RAM 😂 Am Di., 9. Apr. 2019 um 08:21 Uhr schrieb Andre Hartmann < andre.hartm...@iseg-hv.de>: > Hi Martin, > > > What is, when I ignore the ready read? > > The data will stay in the buffer, of course.

Re: [Interest] Parsing data from serialport

Hi Martin, What is, when I ignore the ready read? The data will stay in the buffer, of course. Has the internal buffer a max size? Your RAM or 2^32, whichever is lower. Because at the moment I have a memory leak and maybe it comes from that? I doubt that. A leak would mean, you cannot

Re: [Interest] How to properly show progress for a signal processing pipeline

Am Mon, 8 Apr 2019 16:02:10 + schrieb "Murphy, Sean" : > > I would just show one progress set to 3 * raw count.  Each stage > > periodically signals to the ui thread its progress, and whether it has > > processed the end-of-data signal from the previous stage.  In the ui > > thread slot: > >

Re: [Interest] Parsing data from serialport

What is, when I ignore the ready read? Has the internal buffer a max size? Because at the moment I have a memory leak and maybe it comes from that? Martin Am Fr., 5. Apr. 2019 um 21:12 Uhr schrieb Konstantin Shegunov < kshegu...@gmail.com>: > On Thu, Apr 4, 2019 at 6:42 PM Jérôme Godbout wrote:

Re: [Interest] How to properly show progress for a signal processing pipeline

  08.04.2019, 16:16, "Murphy, Sean" :> We have a data processing pipeline that looks like so:> Raw Data objects -> Type "A" data objects -> Type "B" data objects -> Final Data objects>> Each step can be considered a filtering process where the following mathematical relationship holds for the q

Re: [Interest] How to properly show progress for a signal processing pipeline

> I would just show one progress set to 3 * raw count.  Each stage > periodically signals to the ui thread its progress, and whether it has > processed the end-of-data signal from the previous stage.  In the ui > thread slot: > > int totalCount, rawCount; > > QVector stageProgress; > > void stag

Re: [Interest] How to properly show progress for a signal processing pipeline

Hi, Have a look at Qt Maintenance Tool download meta information progress bar... On 08.04.2019 18:04, Tony Rietwyk wrote: Hi Sean, I would just show one progress set to 3 * raw count.  Each stage periodically signals to the ui thread its progress, and whether it has processed the end-of-data

Re: [Interest] How to properly show progress for a signal processing pipeline

Hi Sean, I would just show one progress set to 3 * raw count.  Each stage periodically signals to the ui thread its progress, and whether it has processed the end-of-data signal from the previous stage.  In the ui thread slot: int totalCount, rawCount; QVector stageProgress; void stageProg

Re: [Interest] How to properly show progress for a signal processing pipeline

So the issue I'm having here is that I want to show the user some sort of progress indicator (this whole pipeline takes a bit of time), but at the start I only know the raw count, not any of the intermediate or final counts. And because the A->B->Final portion of the pipeline takes a notic

Re: [Interest] How to properly show progress for a signal processing pipeline

We have a data processing pipeline that looks like so: Raw Data objects -> Type "A" data objects -> Type "B" data objects -> Final Data objects Each step can be considered a filtering process where the following mathematical relationship holds for the quantities of each type of object:

[Interest] How to properly show progress for a signal processing pipeline

We have a data processing pipeline that looks like so: Raw Data objects -> Type "A" data objects -> Type "B" data objects -> Final Data objects Each step can be considered a filtering process where the following mathematical relationship holds for the quantities of each type of object: R

Re: [Interest] QWebEngine, custom URL schemes and content-types

> On Apr 8, 2019, at 12:46 PM, Andy wrote: > > Not sure if it's the same situation, but I just had a similar problem - SVGs > weren't showing up properly because I had the wrong MIME type. > > I fixed it by using the QMimeDatabase like this: > > const auto cMIMEType = QMimeDatabase().

Re: [Interest] QWebEngine, custom URL schemes and content-types

Not sure if it's the same situation, but I just had a similar problem - SVGs weren't showing up properly because I had the wrong MIME type. I fixed it by using the QMimeDatabase like this: const auto cMIMEType = QMimeDatabase().mimeTypeForData( data ); inRequest->reply( cMIMEType.na

[Interest] QWebEngine, custom URL schemes and content-types

I'm using a custom URL scheme by registering the scheme with QEbEngineUrlScheme::registerScheme() at app startup, creating a handler ("Assets") that inherits from QWebEngineUrlSchemeHandler, installing that scheme handler in the QWebEngineProfile passed to the QWebPage. Assets::requestStarted(