Hello.

Imagine i want to slide a panel down to the y=200 on the screen. from y=0;

i do it: while(panel.pos_y<200){
panel.pos_y+=1*time_step;
wait(1);
}

But sometimes, i check that the final y its not 200, but 199 or something depending on the lag..

How can i avoid that? without the time_step, it gets shaky or slides very quickly.


check this little example with dynamic progress bar...
And you will se that after a while the panels will overlay, showing a one pixel overlay...
Open C file

It is very unlikely that panel.pos_y is precisely 200 after the loop. Example:

- panel.pos_y is 199.873

- assume that time_step was 0.527 in the last frame

- next iteration:

while(panel.pos_y<200){
panel.pos_y+=1*time_step;
wait(1);
}

- panel.pos_y is now 200.4 -> end of loop

I hope you know what time_step does/ is/ how it is calculated. Otherwise have a look at the manual.

Solution:

while(panel.pos_y<200){
panel.pos_y+=1*time_step;
wait(1);
}
panel.pos_y = 200;

Oh superku thats super! though the correction to panel=200 will sometimes be seen, as the panel moves up a little bit, and thats not desireble.. the solution would be using integer maybe?

while(panel.pos_y<200){
panel.pos_y+=1*time_step;
panel.pos_y = minv(panel.pos_y,200);
wait(1);
}

Integer should work, too.

using my example.. and without the time_step to make 199.87 values..
i use this:



but it stills overlay at later.. what im missing?

maybe the scaling is giving incorrect pixel sizes on screen, though the number of the scale is corrected displayed

when i scale up something that is 1pixel on _x , and scaling to 2 , i think it will means 2 pixels ...

when scaling to 50, it will means 50 pixels.. and so on too 100..

although the problem on the start is not showing.. only when the scale reaches (probably 70)

Why don't you use:

while(panel.pos_y<200){
panel.pos_y+=1*time_step;
panel.pos_y = minv(panel.pos_y,200);
wait(1);
}

?

because the example i need more, is more complex than that? did you check it on the top of the post there is a file to download.

i tryed to use the reapeating method of scaling up size_x (that as the manual says will repeat the bmap, which in this case is 1 px lenght...
but what i get it a weird effect like spaced repeating bmap... (i think its not a bug)

and from the manual " The panel size is multiplied with the panel scale."

When i use size_x to move the cap panel on the end, to slide with the repeating one.. that size_x is constant..

So Manual is wrong?

Hi.

To clear confusion about panel scale:

the panel scale is an multiplikator.

The original bmap which is shown on your screen does have scale 1

if you want it double big set scale to 2
if you want it half, set scale to 0.5

so the scale is only an factor.

An example, you have an bmap with 10 X10 pixels.

if you set its scale (scalex and scaley) to 2 it will be displayed with 20 x20 pixels(2 times the height and width of the original)
scale 3 = 30 x30 pixels (3 times the height and width of original)
scale 0.5 = 5 x 5 pixels (half the height and width of the original)

Hope that helps

Greetings

Mike