UI doesnt refresh correctly

mrjj

Hi
Im not sure what you want to use a timer for.
You already have
connect(serial, &QSerialPort::readyRead, this, &MainWindow::on_Serial_Read);

so when data comes, Qt calls your on_Serial_Read

Calling the on_joystick from a timer will not work good as
it will be very out of sync with on_Serial_Read and data in "dizi"
might not been read in yet.

So if you see odd data , it would be that timer seems very fast and at
the first calls, the "dizi" will not have valid values as on_Serial_Read didnt trigger yet.

deleted286

@mrjj my progress bar was stuck on some point. It doesnt see the correct data. I doesnt refresh yourselft when new data comes

mrjj

@suslucoder
Did you check the incoming data ?
Its more likely some unexpected with the data than any refresh problem.

In on_Serial_Read when dont you just call on_joystick ? ( i assume on_joystick is where you set the data to the GUI)

deleted286

@mrjj on serial read, im reading from serial and on_joystick i put the datas on my gui. Where should i call joystick

connect(serial, &QSerialPort::readyRead, this, &MainWindow::on_Serial_Read);
        //connect(serial, &QSerialPort::readyRead, this, &MainWindow::on_joystick);

mrjj

@suslucoder
hi
at the very end of :on_Serial_Read()

so get signal, read data and call on_joystick to display the 14 data you just copied to dizi

deleted286

@mrjj I did it like that. But i dont know why in some data, progress bar doesnt refresh.

mrjj

@suslucoder

well if dont move the bar, the most logical conclusion is that it gets the same value as before.

So put in
qDebug() << "-->"<< dizi[1] << dizi[2]<< dizi[3]<< dizi[4]<< dizi[5]<< dizi[6];
in on_joystick (in top)
and see when it dont move what data, if it still has the same value as before.

deleted286

@mrjj said in UI doesnt refresh correctly:

qDebug() << "-->"<< dizi[1] << dizi[2]<< dizi[3]<< dizi[4]<< dizi[5]<< dizi[6];

I've checked, coming datas are true. Is there anything about threads? I have serial port and i have a gui. There may be something different about it

mrjj

@suslucoder
Hi
Only if you added threads yourself. else it cant be the issue.

So that data is right in top of on_joystick ?
that you are very sure about ?

Since we dont clear dizi between readyRead
it will have old values.

So waht excactly do you see ?
first it work, then it stops. or it never works ?

deleted286

This post is deleted!

mrjj

@suslucoder
Well it cant really be stuck as such.
It means its current value is 15.

You dont have any loops or anything that would prevent it from redrawing ?

I think you will have to use the debugger and set breakpoint on the

ui->progressBarXXXX

and then see when you set data what it is.

Its very unlikely the Widget simply don't redraw as that normally makes them white/odd if
you have strangulated the event loop.

deleted286

@mrjj I didnt understand what you mean. Am i doing something wrong?

mrjj

@suslucoder
Hi
Nope code looks fine but you seem think the widget would suddenly stop to draw and
they rarely do and if they do, then it's very clear as it then looked messed up.

So Im trying to guess at what could be wrong/go wrong.
I think its just something with the data but you seems sure the values are newer and higher than 15 so
I would like you to set a break point on the line where you set the progressbar value
and then run & stop and inspect value in the dubugger to be truely sure that a value higher than 15 comes.

other note, this line
memcpy(dizi, data.constData(), 14);

If less than 14 data comes, then old values are left in dizi.
and what happens if data.constData() is less than 14 ?

I think its something like that.

deleted286

@mrjj data.constData() cant be less than 14. I set it. Its too weird

mrjj

@suslucoder
Hi
What you mean ?
You dont set it at all

QByteArray data = serial->readAll(); <<< this can read all from 1 to xxx bytes

s= data.size(); << this is the size of data we read
if (s>14)  << is is just some variable not related to data
    s=14;

then we copy 14 from data
memcpy(dizi, data.constData(), 14);

so it dont matter how much data we actually got. we always copy 14

deleted286

@mrjj said in UI doesnt refresh correctly:

@suslucoder
Hi
What you mean ?

I have

int16_t dizi[7];

Since I have an array which size is 7, i wrote something

s= data.size(); 
if (s>14)  
    s=14;

mrjj

@suslucoder

But what do you then do with s to make it do anything ?

deleted286

@mrjj Im just try to convert my binary data do int with that code script

mrjj

@suslucoder

ok im not sure what s does.

Anyway, could you try

(in on_Serial_Read)
memset(dizi, 0, 14);
memcpy(dizi, data.constData(), data.size());

in place ot the line
memcpy(dizi, data.constData(), 14);

and tell if it still stops at 15 ?