2020-02-26 05:38 AM
Hello,
Is there a way to add Interaction to every Screen?
I want to have power-off button Interaction which should appear to every screen. This common Interaction would be addition to the other interactions added in Designer.
I figured I could add handleKeyEvent() to FrontendApplication, but that will override all Interactions from all of the Screens.
Is this possible?
If I have 100 screens, do I need to individually add this Interaction to all of them? I hope not, that would be impossible to maintain.
Thanks!
Solved! Go to Solution.
2020-02-27 12:05 AM
Right now its not possible to share interactions. This would be solved by having the designer be able to create a "base" screen that is inherited by sub-screens. We really want to do this - It would make code so much cleaner and reduce the workload.
Hopefully soon!
/Martin
2020-02-27 12:05 AM
Right now its not possible to share interactions. This would be solved by having the designer be able to create a "base" screen that is inherited by sub-screens. We really want to do this - It would make code so much cleaner and reduce the workload.
Hopefully soon!
/Martin
2020-08-07 01:51 AM
@Martin KJELDSEN I would also like to request this feature to reduce the amount of duplication of common interactions for key handling - including to change screen to the previous or startup screens, rather than specifying an absolute screen.
Similarly my other request to list all the interactions so it's easy to spot incorrect/missing ones.
2020-08-10 01:49 AM
Hi @moredatalesscenter,
This is also something we've talked about before. The complex version of this is a complete story board, but i'll try to talk to the designer team about a more simple solution to verify the correctness of the application. Can you think of anything else?
/Martin
2020-08-10 02:07 AM
Martin, that sounds good if there's a way to minimise general interactions that are not screen specific for the application. You mentioned on another post a while back about writing a script to do this post-code generation?
What do you mean by thinking of anything else? I've posted some other questions on other topics while you've been away. More generally, I'm interested in the roadmap and timing for upcoming TouchGFX releases - if they're going to be tied to specific CubeMX versions and when all the bugs reported and feature requests on the forum are being addressed. It feels like there is a good community here who want to make it an even better product than it is already.
2020-08-18 04:49 AM
@Martin KJELDSEN Martin, that sounds good if there's a way to minimise general interactions that are not screen specific for the application. You mentioned on another post a while back about writing a script to do this post-code generation?
What do you mean by thinking of anything else? I've posted some other questions on other topics while you've been away. More generally, I'm interested in the roadmap and timing for upcoming TouchGFX releases - if they're going to be tied to specific CubeMX versions and when all the bugs reported and feature requests on the forum are being addressed. It feels like there is a good community here who want to make it an even better product than it is already.
2024-09-13 03:44 PM
@Martin KJELDSEN Here we are in 2024 - Is this base screen still in the works? Have other workarounds been implemented? Calling screen transitions from a button sampling task would be very easy on projects with large quantities of screens and a few hardware buttons that need to interact with the display.