I noticed something similar with the 2.1.0 Preview for the va-hr yesterday, where onMenu() wasn't being called in the delegate, and was planning to see if it was the same for different targets today.
I'm using the previous SDK (v 1.2.10), I'm talking about the simulator itself.
When pressing & holding the UP button for Settings, just like in the watch, nothing happens,
while all the other buttons are working great.
Has it just always been that way? no settings in the simulator?
For example, I opened an existing CIQ app code named "HRV".
When inside the app, when using the watch itself, I can access the settings of the app itself.
When I compile & run the simulator in Eclipse, I cannot access these settings.
Ok, now I understand what you mean by settings. I've seen this in the 2.1.0 simulator too.. onMenu() isn't being called for some of the target devices - specifically those where the menu Button is a long press for the "up" button (I tried the va-hr, f3, and 230). For devices with a separate menu button (the va and 630 for example), it works fine though
I reported this to Garmin a few days ago, and they opened a ticket.
I was playing with this in the 2.1 preview a few days ago. It looked as though, if the xml defining the device for the simulator in devices.xml includes both long and short press for a button, whichever came first in the list would be honoured, the other would not. So, in fenix3_sim, you have
[PHP]
<key id="UP" behavior="PREVIOUS_PAGE">
<region>
<point x="8" y="244" />
<point x="32" y="238" />
<point x="32" y="282" />
<point x="8" y="276" />
</region>
</key>
<key id="MENU" behavior="ON_MENU" isHold="TRUE">
<region>
<point x="8" y="244" />
<point x="32" y="238" />
<point x="32" y="282" />
<point x="8" y="276" />
</region>
</key>[/PHP]
with which Up works but Menu doesn't; swop them round and Menu works but Up doesn't.
You'll likely see the same thing in devices.xml for the 1.2.x SDK's were it worked properly. It seems to be a bug in how the simulator is handling it with 2.1.0.