Incorrect behaviour when using "next event" in the event modal depending on how zmNinja was started.

[ghost]

Platform & OS Version
iOS: 12.1
Android: 7.1.1
Desktop: Ubuntu 18.04.02, Windows 7, OS X 10.13.6

The version of zmNinja you are reporting:
iOS: 1.3.056
Android: 1.3.056
Desktop: 1.3.056

The version and OS of ZoneMinder you are using:=
Zoneminder: 1.33.6 (1.33.6-bionic)
OS: Ubuntu 18.04.02

What is the nature of your issue
Bug

Details
ZnNinja behaves differently when using "next event" in the event modal depending on how zmNinja was started.

In the "Events List" mode that includes all cameras, one expects to able to select "Footage" for a camera and then select the "next event" control in the event modal to continue to the next event that occurred in time, without regard to which camera generated the event.

However, the actual behaviour depends on how zmNinja was started. If it was started in any other mode than "Events List", it behaves as expected. If it is started in "Events List" mode, selecting "Footage" and then "next event" continues to the next event in time for the currently viewed camera, not the next event in time for any camera.

I see now that if you start in "Events List" mode, switch to another mode and then switch back to "Events List" mode, this behaviour no longer occurs.

zmNinja Debug Logs
ZmNinja log exhibiting correct behaviour. App is started in "Montage" mode. "Events List" mode is then selected and "Footage" is selected for an event that is followed by an event from a different camera. The "next event" control is selected and things work as expected.
zmNinja-logs-Apr-11-19_14-09-21_correct.txt

ZmNinja log exhibiting incorrect behaviour. App is started in "Montage" mode. "Events List" mode is then selected and "Footage" is selected for an event that is followed by an event from a different camera. The "next event" control is selected and we proceed to the next event for the current camera instead of the next event in time.
zmNinja-logs-Apr-11-19_14-10-49_incorrect.txt

[welcome]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you follow the issue template or I may not respond.

[pliablepixels]

thanks - good catch, good reporting.