2022-05-31 05:03 AM
2022-05-31 07:29 AM
it is not happening on simulator. only on my real target !
2022-05-31 07:31 AM
is there any initialization that is running on simulator and NOT on my real target ?
2022-06-01 07:06 AM
today I tried this on evaluation board stm32l496g-disco and it works ok without dots left behind.
the disco has a screen 240*240. my screen is 320*240. can it be the reason to the dots left behind ?
2022-06-03 02:57 AM
Hello @Eblec.1 ,
What do you mean with leaving dots in the path ? Could you provide more details about your issue and maybe also screenshots ?
Something else, next time you post something, please avoid answering to your own post. If you answer your own post, ST teams and other people might think that your issue/question could be answered or at least that someone is already helping you.
So, if you progress with resolving your issue, please edit your post and add news, that's preferable ;)
Thank you !
/Yoann
2022-06-05 11:32 PM
hello, Yoann.
I added an image that shows the dots left by the animation of moving the box through the screen.
thanks.
2022-06-06 05:42 AM
Hello Eblec,
Try use <box>.invalidate() for the background box and execute it in each tick event
2022-06-06 06:09 AM
thanks. I'll try this. but isn't it a workaround to fix an animation problem ?
2022-06-07 12:54 AM
Hello Eblec.1,
You said that on the stm32l496g-disco it works fine but on which board it's not working fine ?
/Osman
2022-06-07 12:58 AM
hello, Oskt.
it works fine on the disco, which has 240*240 screen.
it leaves dots on my custom board with a screen 320*240.
I declare in touchGFX the 320*240 , and only the animation leaves dots.
thanks.