I notice that some Garmin Apps on the F7/Epix Gen2 range display the ability to turn off the touch screen:
Is that functionality available in the Toybox API?
I notice that some Garmin Apps on the F7/Epix Gen2 range display the ability to turn off the touch screen:
Is that functionality available in the Toybox API?
The safest approach is to allow both buttons and touch, as you'll likely have users that prefer buttons, touch, or use both.
Nope, that's just not an option for me: I have too many…
Isn't programmatically disabling touch just intercepting touch messages and returning true without actually doing anything?
I suspect that's a picture of a native activity,
Yes, it's the Garmin "Boating" app.
can disable the touch screen in the simulator with…
I think there's definitely a strong case for providing this capability, but right now it's not available. I'll request it as a new feature and see whether we can get it added in the future.
Brandon, CIQ4.1 is still in beta. 
Normally we see a couple releases before going to GA. So far we have only seen one release, so there are a couple more beta's to sort out the feature. 
Thanks again for the clarification.
It seems you're conflating native apps and Connect IQ apps with activities
Actually whilst the conflation arose from @jim_m_58 and @sabeard, the confusion was all mine. I think they were referring to native apps as activities. Activity recording has always been an intrinsic part of my app, but I have never considered my app an "activity".
The product teams decided to make this option available in the native apps, but this capability is not available in Connect IQ.
I wonder what development environment is available to the developers of native apps?
But anyway, I'm afraid that it'll be far too late for me to benefit from that future. I have to manage it now, by monitoring isTouchScreen and some creative use of Jungles. And with the Sim not accurately simulating that, it's a bit of a challenge. Fortunately I have a co-operative Epix2 owner who is stepping up to be an alpha tester.
Ok I have a solution to disable touch capabilities.
From your class which extends Ui.BehaviorDelegate (Hope you have only one), change from "extends Ui.BehaviorDelegate" to "extends Ui.InputDelegate", thus you will be able to manage touch events too.
Then override like this;
// onTap and onSwipe must return true to not call default behaviour, thus nothing id done during swipe or tap.
function onTap(clickEvent) {
//Sys.println("onTap ");
return true;
}
function onSwipe(evt) {
//Sys.println("onSwipe ");
return true;
}
// then manage buttons with onKey, just call the matching method
function onKey(keyEvent) {
// le button
Sys.println("key event " + keyEvent.getKey());
// ENTER/START
if (keyEvent.getKey() == keyEvent.KEY_ENTER || keyEvent.getKey() == keyEvent.KEY_START) {
return onSelect();
}
// BACK
else if (keyEvent.getKey() == keyEvent.KEY_LAP || keyEvent.getKey() == keyEvent.KEY_ESC) {
return onBack();
}
// UP
else if (keyEvent.getKey() == keyEvent.KEY_UP) {
return onPreviousPage();
}
// DOWN
else if (keyEvent.getKey() == keyEvent.KEY_DOWN) {
return onNextPage();
}
return false;
}
In simulator, all touch capabilities are disable.
Hope it works in real.
I have used only sourcePath, my "input listener" for vivoactive and venu are in a directory, and the listener for fenix, forunners... is in another directory .... and according to the device the good class is loaded, this is not a problem.
Generally speaking I have 1 sourcePath directory for common features and 1 or more for device specificities
-> I undertand your position/angry, doing an app can take many times (more than 1700 hours for my main app, yes 1700 not 170) and it is a personal investment, more over unjustified bad reviewes are not easy to understand, not easy to understand that somebody prefer post a bad review than contact you!
And I see your app is free.... and target a little market... respect, you have my support
