Share via

Azure RTOS GUIX Studio new 6.4.0.0 update breaks the application i am maintaining.

Alexandre Tremblay 0 Reputation points
2025-06-23T15:20:04.87+00:00

The new 6.4.0.0 update added a protection against the use of an empty widget when calling functions on a button press for example. events are not beign called anymore on the application that was created and worked fine for the last 10 years.

The application calls the function to switch windows, empty the widgets once done and does not send the event of button pressed anymore to the back end since the widget is null. the back end never needed the widget info, only the event.

is there a way to use an older version of GUIX Studio or are we forced into new releases?

A more permanent solution than modifying the source files compiled by GUIX Studio is the goal without it requiring modification to the whole application to fit the new rule added.

Azure RTOS
Azure RTOS
An Azure embedded development suite including a small but powerful operating system for resource-constrained devices.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Manas Mohanty 13,340 Reputation points Moderator
    2025-06-23T18:13:19.76+00:00

    Hi Alexandre Tremblay

    You're encountering a known issue introduced in GUIX Studio 6.4.0.0, where the auto-generated gx_studio_auto_event_handler() function now includes stricter checks that prevent events from being sent if the widget is null—even if the backend doesn't rely on widget data. This change has disrupted legacy applications that previously worked fine without widget validation.

    Current Workarounds and Solutions

    1. Modify the Auto-Generated Event Handler (Temporary Fix) Developers have found that modifying the gx_studio_auto_event_handler() function to delay widget detach/delete operations until after all actions are processed can restore expected behavior. However, this is not a permanent solution since GUIX Studio regenerates this file on each build Reference - https://github.com/eclipse-threadx/guix/issues/66
    2. Use an Older Version of GUIX Studio You can download and use older versions of GUIX Studio from the official GitHub releases page For example, version 6.3.0 does not include the stricter widget validation logic introduced in 6.4.0.0. Permanent Fix Without Modifying Entire Application If downgrading is not viable, consider creating a wrapper or proxy widget that persists through the event lifecycle and passes the event to the backend, even if the original widget is deleted. This would require minimal changes to your application logic.

    Recommendation

    If your goal is to avoid modifying the entire application and maintain long-term stability:

    • Downgrade to GUIX Studio 6.3.0 or use latest version 6.4.2 (if studio installation is needed), which does not enforce the new widget validation rules.
    • Alternatively, request a feature or configuration flag from the maintainers via GitHub Issues to allow disabling widget validation for legacy compatibility.You're encountering a known issue introduced in GUIX Studio 6.4.0.0, where the auto-generated gx_studio_auto_event_handler() function now includes stricter checks that prevent events from being sent if the widget is null—even if the backend doesn't rely on widget data. This change has disrupted legacy applications that previously worked fine without widget validation.

    Hope it helps

    Thank you.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.