Acknowledged
5 days ago
CIQQA-3251

Introduce new state for AppBase.onStart method when sensor pairing (CIQ System 8)

It would be helpful to have a way to determine whether the initialized application (AppBase) is being launched specifically for sensor pairing. This would allow the application to initialize only the components necessary for pairing.
In my case, the data field opens an ANT channel in the AppBase.onStart() method, which I want to avoid when the application instance is being used for pairing. As a workaround, I currently release the ANT channel when AppBase.getServiceDelegate() is called.
To address this more cleanly, I propose introducing a new state or flag within the onStart() method that indicates when the application has been launched from the Sensors menu.

maca88
Parents
  • 5 days ago

    This is a good feature request, but until it's implemented, could you open the ANT channel in getInitialView() instead?

    >  As a workaround, I currently release the ANT channel when AppBase.getServiceDelegate() is called.

    I assume this is a typo and you mean getSensorDelegate

Comment
  • 5 days ago

    This is a good feature request, but until it's implemented, could you open the ANT channel in getInitialView() instead?

    >  As a workaround, I currently release the ANT channel when AppBase.getServiceDelegate() is called.

    I assume this is a typo and you mean getSensorDelegate

Children
  • 5 days ago in reply to FlowState

    > Could you open the ANT channel in `getInitialView()` instead?

    I initially thought that getInitialView() wouldn't be called for a data field unless it was in the foreground (that is, on the currently displayed data page). However, after running some tests, I realized I was mistaken. getInitialView() is called regardless of which data screen the field is on. So yes, placing the ANT channel opening in getInitialView() is a better approach for now. Thanks for pointing that out!

    > I assume this is a typo and you meant getSensorDelegate.

    Good catch, yes, I meant getSensorDelegate. Unfortunately, I am not able to edit the bug anymore.