Acknowledged
CIQQA-4730

Button "Back" closes an Connect IQ aplication when it is pressed in Confirmation view

Hello! 

I would like to report about very old issue with Confirmation View. When I added it into my application TimeToSail to confirm Exit I found this problem. If you press Back callback function response() is not called, but application is closed suddenly. There is no way to handle Back button actions, like it is implemented in other delegate classes. I expect that ConfirmationDelegate should ignore pressing button, except Accept and Cancel buttons. 

Hope you to fix the issue. There are several reports on the forum during last 4 years.

 Back button in Confirmation Delegate 

 Back in confirmation quits app instead of popping (Vivoactive 3)  

Thank you in advance

Best regards

Konstantin

Piligrim
Parents
  • in reply to jim_m_58

    When you use mouse, do you click on the pictures of buttons? I expect you do so. You just simulate pressing of hardware buttons. From the software point of view these actions are same. The main idea is that on simulator button Back (lower right button) is used as Confirmation button. So it generates response() function call. 

    On the device the lower right button Back generates something strange. And you cannot handle this action, since ConfirmationDelegate doesn't allow to override onBack processing.

    By the way, I recommend to your team (are you from Garmin?) to implement such possibility. Let people to override handling of ANY key pressing. Like it is done in other delegates, eg MenuDelegate etc.

Comment
  • in reply to jim_m_58

    When you use mouse, do you click on the pictures of buttons? I expect you do so. You just simulate pressing of hardware buttons. From the software point of view these actions are same. The main idea is that on simulator button Back (lower right button) is used as Confirmation button. So it generates response() function call. 

    On the device the lower right button Back generates something strange. And you cannot handle this action, since ConfirmationDelegate doesn't allow to override onBack processing.

    By the way, I recommend to your team (are you from Garmin?) to implement such possibility. Let people to override handling of ANY key pressing. Like it is done in other delegates, eg MenuDelegate etc.

Children
  • in reply to Piligrim

    I'm not Garmin but I've been doing apps since 2015.  I have a number of devices I can test with, back to original vivoactive.  As I've said before in many cases how the sim does things, it is "generic"  You may want to get another device - like maybe one without touch or one with only two buttons.