How to display the result of an operation in incremental fashion strating from 0?
-
@Colins2 im not 100% sure what you need to do but see
int32_t cnt = 100; QString msg, cno; QTimer *ltimer = new QTimer(); //do{ // QTextStream(&cno) << cnt; //msg = ("Hello left no : "+ cno); QObject::connect(ltimer, &QTimer::timeout,[&](){ cnt--; if(cnt == 0){ // < ltimer->stop(); } qDebug()<< ("Hello left no : " + QString::number(cnt)); }); cno.clear(); // QThread::sleep(1); ltimer->start(10); // }while(cnt > 0); -
-
@Colins2 im not 100% sure what you need to do but see
int32_t cnt = 100; QString msg, cno; QTimer *ltimer = new QTimer(); //do{ // QTextStream(&cno) << cnt; //msg = ("Hello left no : "+ cno); QObject::connect(ltimer, &QTimer::timeout,[&](){ cnt--; if(cnt == 0){ // < ltimer->stop(); } qDebug()<< ("Hello left no : " + QString::number(cnt)); }); cno.clear(); // QThread::sleep(1); ltimer->start(10); // }while(cnt > 0);@LeLev
I don't think your solution is what I want.What I am trying to achieve is quite simple - or should be.
I have a PlainTextEdit widget that I am using as a log output.
At various times through different routines, I want to output a message.
What happens is that I get no output until the end of the routine, which isn't much use.I just cobbled the above routine to try to get just the message output working. It has no real relevance to my project other than the method.
My loop just created a message with the counter attached and I would expect it to print to the PlainTextEdit widget when called.
It doesn't do that. Stepping through the code, the statement executes and then the loop continues but nothing appears in the edit field. At the end of the loop it all gets dumped in one go.Re. the QTimer, It's new to me. I've never had to use these types of function to get output on the screen.
As Gerd says in his post, it should be such a simple thing to do but it appears not to be. -
@LeLev
I don't think your solution is what I want.What I am trying to achieve is quite simple - or should be.
I have a PlainTextEdit widget that I am using as a log output.
At various times through different routines, I want to output a message.
What happens is that I get no output until the end of the routine, which isn't much use.I just cobbled the above routine to try to get just the message output working. It has no real relevance to my project other than the method.
My loop just created a message with the counter attached and I would expect it to print to the PlainTextEdit widget when called.
It doesn't do that. Stepping through the code, the statement executes and then the loop continues but nothing appears in the edit field. At the end of the loop it all gets dumped in one go.Re. the QTimer, It's new to me. I've never had to use these types of function to get output on the screen.
As Gerd says in his post, it should be such a simple thing to do but it appears not to be.@Colins2 said in How to display the result of an operation in incremental fashion strating from 0?:
At various times through different routines, I want to output a message.
If I understand you correctly this will not happen in a loop in your main thread - is that correct?
Is your current implementation with the loop just proof of concept (or an example)?
As I explained already your loop is blocking the event loop that's why it behaves like it does.
So, the question is: how are these messages generated and exposed? -
@JonB
The idea was to trigger the timer stop so that I could print the current message and then resume.
I see what you mean though, it shouldn't be necessary to re-connect every time, just start and stop.@Colins2
It's not just that it shouldn't be necessary, your loop will create a brand new, duplicate connection each time round the loop. You will end up with hundreds of slots on the timer's signal.This code really shouldn't be difficult! Though I'm not offering to write, and I'm Python/PyQt anyway. You have to have something which allows the Qt event loop to run if you want to see the output come up as you go along. If your new data arrives from somewhere externally, you might raise a signal and have a slot to update your display. That will be happening within the Qt main event loop, so all will get updated as you go along.
I see @jsulm is responding more to what you want, I'll leave it to him :)
-
@Colins2 said in How to display the result of an operation in incremental fashion strating from 0?:
At various times through different routines, I want to output a message.
If I understand you correctly this will not happen in a loop in your main thread - is that correct?
Is your current implementation with the loop just proof of concept (or an example)?
As I explained already your loop is blocking the event loop that's why it behaves like it does.
So, the question is: how are these messages generated and exposed?@jsulm
Yes, it will happen during the loop execution, that is the whole point of my problem.Rather than talking abstract things, this is what I want to do:
I have a large plain text file (300k+) which is an airport database in a flight sim.
The entries are formatted according to their specs with all entries in plain text to make it easy to read in a text editor if desired.
There are over 28000 entries in there.
There are some formatting errors also that stop me from processing the data as I wish.
I have a program that I wrote in Rad Studio that does exactly what I want.
It reads every entry, skips the fields I don't want, collects various statistics and file locations that I do want and gives me the output that I am looking for. While processing, it will print whatever I tell it on the screen in a memo field.
I used this to good effect when trying to get around some of the wrongly formatted data that was crashing my program, i.e. finding out where it was crashing, and on which entry.
I have got a program that runs error free now and will print out the erroneous entries as they occur so that I can manually edit the file and correct them.I have no problem with Rad Studio, I have been a C++ Builder user for years but it only works on Windows. As the sim runs on MacOS and Linux as well, I wanted to try to write the same program that I could compile on all 3 platforms, hence the use of Qt.
-
@jsulm
Yes, it will happen during the loop execution, that is the whole point of my problem.Rather than talking abstract things, this is what I want to do:
I have a large plain text file (300k+) which is an airport database in a flight sim.
The entries are formatted according to their specs with all entries in plain text to make it easy to read in a text editor if desired.
There are over 28000 entries in there.
There are some formatting errors also that stop me from processing the data as I wish.
I have a program that I wrote in Rad Studio that does exactly what I want.
It reads every entry, skips the fields I don't want, collects various statistics and file locations that I do want and gives me the output that I am looking for. While processing, it will print whatever I tell it on the screen in a memo field.
I used this to good effect when trying to get around some of the wrongly formatted data that was crashing my program, i.e. finding out where it was crashing, and on which entry.
I have got a program that runs error free now and will print out the erroneous entries as they occur so that I can manually edit the file and correct them.I have no problem with Rad Studio, I have been a C++ Builder user for years but it only works on Windows. As the sim runs on MacOS and Linux as well, I wanted to try to write the same program that I could compile on all 3 platforms, hence the use of Qt.
@Colins2
At the risk of (a) predicting and (b) infuriating @jsulm (who, btw, does know what he is talking about), I believe he will recommend putting your large file reading code into a separate thread, so that it does not block the UI since it takes so long to read/process. Send send signals from that thread to a slot in the main UI thread which updates the memo field. You will see output as you go along.Now, I really hope he does not scream at me, but if you want a rough & ready solution while you await his input, @Gerd's
or..
just add a
QApplication::processEvents();right after
ui->product->display(temp);
will (I think) probably get you by without a separate thread, for this case... !
-
@Colins2
At the risk of (a) predicting and (b) infuriating @jsulm (who, btw, does know what he is talking about), I believe he will recommend putting your large file reading code into a separate thread, so that it does not block the UI since it takes so long to read/process. Send send signals from that thread to a slot in the main UI thread which updates the memo field. You will see output as you go along.Now, I really hope he does not scream at me, but if you want a rough & ready solution while you await his input, @Gerd's
or..
just add a
QApplication::processEvents();right after
ui->product->display(temp);
will (I think) probably get you by without a separate thread, for this case... !
-
@Colins2
At the risk of (a) predicting and (b) infuriating @jsulm (who, btw, does know what he is talking about), I believe he will recommend putting your large file reading code into a separate thread, so that it does not block the UI since it takes so long to read/process. Send send signals from that thread to a slot in the main UI thread which updates the memo field. You will see output as you go along.Now, I really hope he does not scream at me, but if you want a rough & ready solution while you await his input, @Gerd's
or..
just add a
QApplication::processEvents();right after
ui->product->display(temp);
will (I think) probably get you by without a separate thread, for this case... !
-
@JonB @J-Hilk
I had thought about it the other way round, i.e. how to create a separate thread for the messages and progress bar but your idea sounds the better way.
Thanks for everyone's input@Colins2
In Qt you don't have a choice about this: all UI operations must be performed in the main thread (not sure how that's defined, maybe the one where you callQApplicationfrom), any non-UI can be performed in separate threads, but not the other way round.Hence in Qt: "All threads are equal, but some are more equal than others" :)
-
@Colins2
In Qt you don't have a choice about this: all UI operations must be performed in the main thread (not sure how that's defined, maybe the one where you callQApplicationfrom), any non-UI can be performed in separate threads, but not the other way round.Hence in Qt: "All threads are equal, but some are more equal than others" :)
