UI doesnt refresh correctly
-
@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
-
@mrjj I did it like that. But i dont know why in some data, progress bar doesnt refresh.
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. -
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.@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 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
@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 ? -
@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 ? -
This post is deleted!
@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. -
@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. -
@mrjj I didnt understand what you mean. Am i doing something wrong?
@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.
-
@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.
-
@mrjj data.constData() cant be less than 14. I set it. Its too weird
@suslucoder
Hi
What you mean ?
You dont set it at allQByteArray 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
-
@suslucoder
Hi
What you mean ?
You dont set it at allQByteArray 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
@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 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;But what do you then do with s to make it do anything ?
-
But what do you then do with s to make it do anything ?
-
@mrjj Im just try to convert my binary data do int with that code script
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 ?
