I have created one sample project based on sample battery charging example project and implemented single simulation timer trigger the system event handler
1. First two count it goes to first screen
2. Third count it does not navigate to second screen .
the implementation of the method TriggerEvent2() triggers still the first instance of the System Event. Is this intended?
Shouldn't it be SystemEvent2 (with 2 at its end)?
Hi Paul its my mistake ,
I made a correction and but still the output is same , i have resend the project
please note the error message reported when the application is running in Prototyper:
The value param is null:
that was the mistake of systemEventHandler2 was not linked .
I crossed check param is receiving the value but still it does not go into the second screen https://ask.embedded-wizard.de/?qa=blob&qa_blobid=4785939336840213068
so far I see in your project, the SecondApplication component is not used within the application. You will need to create an instance of the component and present it explicitly. For example, FirstApplication is embedded within ApplicationRoot. In this way it 'exists', it is visible and can react to events.
Possibly, you should embed also the SecondApplication within ApplicationRoot? Or you create an instance of SecondApplication dynamically when ApplicationRoot receives some event? Which approach you select, depends on the effect you want to achieve and your expected application structure.
Does it help you further?
Ask Embedded Wizard
Welcome to the question and answer site for Embedded Wizard users and UI developers.
Ask your question and receive answers from the Embedded Wizard support team or from other members of the community!