Using the simple standard config as a base, I upgraded an existing 2.0 config to 2.1 and encountered some programming compile errors where there were duplicate named events. One of those was in the DM2 program involving the Leave 'Dm2 to Initial State'.
I attempted to rename the event and it compiled, but now after running the DM2 query there seems to be no way to return to the menu. I can't find the DM2 page to add the button to return to the menu either.
DM2 2.0 -> 2.1 upgrade - Can't return to menu
- tthomas
- Posts: 7
- Joined: Tue Sep 21, 2010 1:10 pm
- jpurdum
- Enovation Controls Development
- Posts: 153
- Joined: Mon Jun 21, 2010 11:19 am
Re: DM2 2.0 -> 2.1 upgrade - Can't return to menu
I'm going to answer why you couldn't find the screen first:
The DM2 application is still a separate application - held over from the 1.0 days. In other words, it's not a configured screen, it's an application that draws to the screen directly. So, you won't find it's screen in the configurations. However, it's buttons are defined in the Popup Layer on the screen named "DM2". So basically, an action is sent to the DM2 app to tell it to show itself, and these buttons then are placed on top of it to receive key inputs.
The issue of not able to return to menu:
Yes, in the upgrade process we have more stringent checks on duplicate names etc. There is an event in the 2.0 set of configurations called GoToInitalState used in state machine named "DM2". An event with the same name was used in the UserSettingsSave state machine.
In the DM2 state machine, look for the state "Leave Dm2". In that state, there was an action for CCM->FireEvent(GoToInitialState). It looks like in these configs, this particular event was defined outside this state machine, so when you renamed it, you probably actually create a whole new event. If you look at the action call in the "Leave Dm2" state, it probably still says CCM->FireEvent(GoToInitialState). Just change the event it's sending to the new name you gave the event between "Leave Dm2" state and the "Initial State" state.
Let me know whether that was the issue.
jcp
The DM2 application is still a separate application - held over from the 1.0 days. In other words, it's not a configured screen, it's an application that draws to the screen directly. So, you won't find it's screen in the configurations. However, it's buttons are defined in the Popup Layer on the screen named "DM2". So basically, an action is sent to the DM2 app to tell it to show itself, and these buttons then are placed on top of it to receive key inputs.
The issue of not able to return to menu:
Yes, in the upgrade process we have more stringent checks on duplicate names etc. There is an event in the 2.0 set of configurations called GoToInitalState used in state machine named "DM2". An event with the same name was used in the UserSettingsSave state machine.
In the DM2 state machine, look for the state "Leave Dm2". In that state, there was an action for CCM->FireEvent(GoToInitialState). It looks like in these configs, this particular event was defined outside this state machine, so when you renamed it, you probably actually create a whole new event. If you look at the action call in the "Leave Dm2" state, it probably still says CCM->FireEvent(GoToInitialState). Just change the event it's sending to the new name you gave the event between "Leave Dm2" state and the "Initial State" state.
Let me know whether that was the issue.
jcp
- tthomas
- Posts: 7
- Joined: Tue Sep 21, 2010 1:10 pm
Re: DM2 2.0 -> 2.1 upgrade - Can't return to menu
[Resolved]
I double checked the re-naming of the events, but i think the root cause was the lower left button on the DM2 popup layer was missing the event call 'KeyExitDm2Application'. So the application was ok; however nothing was triggering the return to menu event.
Thanks for your help
I double checked the re-naming of the events, but i think the root cause was the lower left button on the DM2 popup layer was missing the event call 'KeyExitDm2Application'. So the application was ok; however nothing was triggering the return to menu event.
Thanks for your help