Menu view popping (in sim)

My app has the app view -> menu view 1 -> menu view 2

For the Edge 1000 (a CIQ 2.4 device), in the simulator clicking the back button in menu view 2 pops all the way back to the app view.

For the Edge 1030 (a CIQ 3 device), in the simulator clicking the back button in menu view 2 pops back to menu view 1 (as expected).

Is the 2.4 issue a general one or is it just in the simulator?

jim_m_58 over 6 years ago

I threw together something simple using the Device App template in Eclipse. Press menu, then press the first menu item and a second menu gets pushed, and it seems to work fine in the sim for the 1000 and 1030. back on the second menu returns to the first

Update: it also worked correctly on a sideload to the edge 520 (with a 2.4.6 VM)
When you select something on the 2nd menu, you also return to the 1st menu.

Here it is.

jim_m_58 over 6 years ago

Basic flow:

Main view delegate
  -onMenu pushes 1st menu
  1st menu delegate
    -first menu item pushes 2nd menu and does println 
    -second menu item does println
    2nd menu delegate
      -both menu items do a println

The views are not popped in the code.

dpawlyk over 6 years ago

The views are not popped in the code.

My code isn't popping them.

I'm pushing the first menu in onSelect().

The onBack (which can't be overridden) on the second menu skips over the first menu in CIQ < 3.

In CIQ 3, things are working as expected.

jim_m_58 over 6 years ago

Does it work in the app I posted? (if you can't get the .zip - forum problems - use "Contact Developer for this so I can get your email and email it to you)

You probably need to post some of your code, as it should work in your app too.

Travis.ConnectIQ over 6 years ago

I'm pushing the first menu in onSelect().

If you're using onSelect in your delegate, then you're using Menu2.. Right?

Menu2 isn't supposed to be available to devices prior to ConnectIQ SDK 3.0.

jim_m_58 over 6 years ago

Travis, Menu2 on a e1000 causes a "symbol not found" (as it should), so I'm thinking it's Menu, but something is odd in the Menu Delegate (maybe it's the Menu2 "style" delegate?). That's where seeing the code for that would help.

dpawlyk over 6 years ago

If you're using onSelect in you're delegate, then you're using Menu2.. Right?

Menu2 isn't supposed to be available to devices prior to ConnectIQ SDK 3.0.

It's using onMenu on CIQ < 3. (You can have have a onSelect but it won't be called.)

I'll look at Jim's code on Monday.

jim_m_58 over 6 years ago

With the app I posted, I changed onMenu to onSelect in the main view delegate, and it works fine for the 1000 and 1030 - it's a screen tap. What wasn't working for you?

dpawlyk over 6 years ago

With the app I posted, I changed onMenu to onSelect in the main view delegate, and it works fine for the 1000 and 1030 - it's a screen tap. What wasn't working for you?

I misspoke a bit (I said onMenu instead of onMenuSelect).

The menu2 delegate uses onSelect for picking a menu item.
The menu delegate uses onMenuItem for picking a menu item.

The issue isn't with pushing. It's with popping.

The back from the second menu skips the first (in CIQ < 3)

main -> menu-1 -> menu-2

jim_m_58 over 6 years ago

The app I posted uses onMenuItem in both menu delegates.

In the delegate you use onSelect with Menu2 and onMenuItem with Menu. Menu2 is the the new version of Menu that was introduced in 3.0.0, not the second menu..