Help us make the next TouchGFX release even better!

[Soren Myllerup MIKKELSEN]

We are getting a lot of new ideas, which we are discussing internal, but getting your feedback and vote on each idea would be very helpful. So please go to below link and submit your vote and any feedback you might have.

List of some of the ideas:

• Add ARGB1555 image format.
• Fast start with LVDS displays in TouchGFX
• Allow modal window without specifying a background image
• TouchGfx Expandable Side Screen for Interactions

You can find the rest here: https://community.st.com/s/ideazone?t=1604315637197#list

[HP_it]

Just a friendly nudge towards all those ideas that have been generated since you posted this. Most of the ideas are just sitting there. What is the procedure for either accepting the ideas or rejecting them?

A lot of them are really good - It would be so nice to know if we can expect to see them introduced in upcoming versions :)

[Asantos]

Rewrite it in C.

Better step by step tutorial.

[Bob Bailey]

Official support in the code and application templates for NVM storage of settings, defaults, states, etc. for screen elements. There have been several threads lately specific to this issue, eeprom emulation and SDMMC would be the storage locations needed. The implementation would need to handle control of memory mapped mode control of QSPI/OSPI if storing to those devices. The same updates to the applications could include basic implementations of message queuing to TGFX from a user task, and from TGFX to a user task for control based on screen events and settings changes (sliders, etc.)

Bob

[Soren Myllerup MIKKELSEN]

@HP​ 

All those ideas are very appreciated. We try to discuss each one of them, and set a status afterwards. Some of them is required more information, and all of them needs more votes from you the community, as it is not easy decide which one is most relevant for our users.

The process is to review, request more info, and then to reject or accept.

We are a bit behind, but we will get there to answer them all. And some of them will be introduced soon.

@Community member​ 

For the step by step tutorial, i believe you are referring to this site: https://support.touchgfx.com/docs/introduction/welcome

We believe the overall documentation site is serving as a step by step, but maybe not touching all cases. If you have specific inputs, please share.

@Bob Bailey​ 

Thanks for sharing the detailed input. I will have the engineering team to address the possible improvements/new features.

Hope you all are enjoying the holidays. Happy new year :)

[HP_it]

Thank you for the clarification!

It was by no means meant at a slap to the face - I think you're all doing a great job and I know you are working **** ** the next iteration already :)

[Lagodolio]

I think it should be useful if you add a new trigger in Buttons (Normal buttons, Flexible Buttons, etc): "unclicked" .

So a user can send a command when push down the button and send another command when the button is released.

Thanks a lot for your great job!

[JStei.6]

Would it be possible to implement an option that lets us choose if we have a B-LCDAD-HDMI / B-LCDAD-RPI1 connected to a STM32f669i (or similar boards) and that auto-generates the code for it? currently it´s much work to implement those two.

If thats not possible, a step by step tutorial on how to use those two with touchGFX would be very helpful.

Thanks!

[Romain DIELEMAN]

Hi,

I am unfamiliar with this but I believe it would be something to set with STM32CubeMX or through user code ? Have you done it yourself once or know where we could get the code ?

/Romain

[FDick.1]

I think it might make sense to make the common display and touch driver IC (e.g. st7789 or ili9341) selectable on a custom board via SPI in TouchGFX, maybe as a example. I wrote a driver (CubeIDE) myself, but it doesn't even go into the from TouchGFX generated function "void TouchGFXHAL :: flushFrameBuffer (const touchgfx :: Rect & rect)". I don't find any hints online what I have to pay attention to apart from adding the functions. So here I would like more information. Because only doing the things that are in the instructions (https://support.touchgfx.com/docs/development/touchgfx-hal-development/scenarios/scenarios-spi#transfering-the-framebuffer) doesn't help and lead to some error messages in the cubeIDE. I also only find example code that uses FMC, but I would like to use SPI, so I can't use the drivers for the ICs that are used there either. The support for custom boards is rather low.

Best regards!

[Romain DIELEMAN]

Hi,

​

You are right concerning the support for custom boards, we actually talked about it this morning again :grinning_face_with_sweat:. We provide ATs for the ST development kits but it makes sense to have a section/video or project on this.

Meanwhile I actually found this youtube video on TouchGFX on SPI-based ILI9341 (partial framebuffer strategy). There is this older post on reddit as well, he might have been able to make it work since then.

/Romain

[FDick.1]

Hi, thanks a lot for your tips. I looked at the site https://helentronica.com/2021/01/22/touchgfx-on-a-custom-made-low-cost-board-with-the-ili9341-controller-over-spi/ , I use the STM32F429I-DISCO board, then selected touchgfx as software pack here in CubeMX and then made the appropriate settings for my extern SPI display (240x240 pixels) with the St7789. On the above mentioned page it says that in the TouchGFXGeneratedHAL.cpp the following function is defined: But in my project the function is not defined in the mentioned file. Since this is in the read-only zone, I can't just paste it in, have I defined something wrong or forgotten something? Do I have to change a setting in CubeMX for this?

Sorry if this question is in the wrong place.

[wired]

If a widget is moved from one screen to another, automatically move its related interactions to the other screen screen, or at least allow interactions to be dragged into another screen. Also update other related information automatically. I moved a bunch of widgets from one screen to another, and it took me forever to get everything updated. It also messed up the Single Use Texts information, leaving entries blank that I could not delete unless I converted them to Resources and deleted them.

[wired]

Allow any button to be a Repeat Button. Would be especially useful for Icon Buttons (Up, Down, Left, Right Arrow)!

[Romain DIELEMAN]

Thank you very much for your ideas:thumbs_up:Concerning the repeat functionality, the Repeat button widget and the Flex button widget are meant for those scenarios.

/Romain

[wired]

Hi Romain,

Yes I know the Repeat button is for the Repeat function ;), but you cannot add a text label or icon to the repeat button, which makes it rather useless IMO. It would be much more user-friendly to be able to enable that functionality with any button. In fact, I would argue that it would be more user friendly to have only one button type in which all of the properties of the others could be used, without having to 'build' a button like you have to do with a Flex button (which looks crappy by default - 'box' and 'box with border' are really not the button quality we expect from TouchGFX).

Your Button with Icon, for example, shows an Icon on the left side of a long rectangular button. There is plenty of room to have a label on the button, yet the properties do not allow a label. All of the 'Round Edge buttons (Small, Medium, and Large) for example, look ridiculous with an icon and no label.

You also stated the Flex Button is meant for Repeat Functionality. I can find no properties for repeat functionality for a Flex button. But you are right, there should be!