3 bugs

[TDJ]

1. TouchGFX Designer looks for ST-Link utility in:

C:\Program Files (x86)\STMicroelectronics\STM32 ST-LINK Utility\ST-LINK Utility

while recent ST-Link version gets installed in:

C:\Program Files (x86)\STM32 ST-LINK Utility\ST-LINK Utility

and different folder selection during installation is not even an option.

2. Slider control has a bug, handle leaves a trace while moved - both in emulator and on STM32F769i-DISCO. See screenshot.

3. Change Screen interaction action does not seem to always work. Controls from another screen appear but controls from the previous screen do not slide out - for example. In emulator it works OK, on STM32F769i-DISCO it does not.

It is great product, just little buggy.

[Martin KJELDSEN]

Hi,

Thanks!

1) I'll investigate. Could you show me a log/screenshot of the error you're getting?

2) It's not a bug =) You're missing a background. Right now you're basically drawing (and invalidating) on top of garbage data in the framebuffer which will leave "traces". It's a common mistake by users and we've considered always adding a default background to avoid confusion.

3) Maybe you do not have a buffer defined for effects like transitions (requires a seperate buffer called "animation storage"). It's required for hardware configuration - For simulator there's always enough memory to do it.

So, while the majority of your list most likely do not qualify as "bugs" the fact that you're experiencing it tells us something about the usability of TouchGFX - That's great feedback actually.

Let me know.

/Martin

[TDJ]

1. Screenshot attached. Btw, line-wrapping may be a good log viewer improvement.

2. OK, let's call it a feature:) Although I think in YouTube presentations it worked as expected without additional settings.

3. The observed behavior differs much between emulator and STM32F769i-DISCO board I use for tests which may be a sign of weakness.

Btw, some YouTube tutorial on how to use TouchGFX with CubeIDE for this board would be highly appreciated.

I am not Eclipse enthusiast but CubeMX could be useful. Could be since I have not succeeded trying to configure graphic for this board yet.

VS project uses tools ver. 100. Maybe it is good idea to switch to some never version. Who uses VS 2010 anymore?

[Martin KJELDSEN]

1. Thanks. We're discussing options for this. The path is hard coded in the Makefiles.
2. It's a feature for now, at least : ) Maybe we'll do something to notify the user that unmodified framebuffer memory is visible.
3. Can you describe this observed behavior?

You can upgrade the MSVS toolset to your current version. We supply libraries for all versions of MSVS (2010 is lacking 2019 because it was released a while ago).

/Martin

[Martin KJELDSEN]

Hi Tomasz,

No problem! The project is v100 because it's the lowest common demoninator, and fortunately, whenever you open a project in a later version you're prompted to upgrade the toolset. If we made it v140 then it would be the same issue for people with newer versions. and we don't want to make projects for every specific version.

Some still use legacy compilers like v100 - Certain companies can take a long time to switch compiler.

Hope that answers your concern.

Best regards,

Martin

[TDJ]

My point was v100 no longer appears to be the common denominator.

Who uses VS 2010 anymore? - besides 'certain companies', of course.

And those who still use VS 2010 probably have been around long enough so they do not need TouchGFX.

Anyway, it is just my guess. Probably you have exact telemetric usage data and I am completely wrong.

Best,

Tomasz