Currently, POI positioning is relative to (0,0) being bottom-left. Map Editor positioning is relative to (0,0) being top-left. Change algo accordingly.

When the user attempted to start a storyline from elsewhere, he is proposed to navigate to the starting point first.

From @ericlam51
Now, upon arrival at the starting point, automatically start the storyline

The zoom range is wrong, smallest zoom is to big therefore we cannot have an overview of the map. And the biggest zoom is too big and irrelevant since we can't see nothing

Clicking on a notification while viewing an image full screen or viewing a video does not bring back the user to the correct floor; it brings him back to the map fragment where he left off

When running unit tests on JSON generators for POIs and Floor information to send to javascript side, the order of the attributes is not the same as the expected output when on certain machines.
Refer to pull request #5

MAPX390-48

When navigating to a POI and I reach another POI on my way to the desired POI, say navigating from POI 7 to POI 1 and I pass by POI 6 I still see the path from POI 7 to POI 6 until I click the notification. Even if my new location is POI 6

Steps:

1. Click on a POI to start navigation mode.
2. Cancel Navigation mode.
3. Start Storyline mode.
4. Path of previous Navigation mode is drawn.

Rationale
After mode is cancelled, path is not set back to null. In the current situation, where Storyline mode returns nothing, the previous path is kept, and is being displayed. While this should not happen in production (when Storyline mode is complete), it is a safer bet to reset path to null after every mode cancellation.

This also comes into tie with a second issue, while looking through the code. On MapManager, line 167, here is the following code:

MapJSBridge.getInstance().leaveNavigation();

This should instead be leaveCurrentMode() so that all the proper variables are reset (ie: the path). Just an FYI.

When in navigation mode and trying to start a storyline, the toast saying that the storyline has started appears before the user has confirmed that he wants to leave navigation mode and start the storyline

The current list view recycles each view with its property, meaning that a recycled expanded view will be recycled and rendered as an expanded view even if the new view is not to be expanded

This call does not work: $("a [data-floorId = '"+floor+"']").click()
first it should be $("a [data-floorId = '"+floor+"']")[0].click()
But then this works however the element returned is empty
see in PR #36

The application crashes after multiple notifications and image/video viewing. When clicking back afterwards, it brings back the user to the map fragment but does not re-enable the drawer

When changing the screen orientation, the application always returns to the map view

Open the pop up and add the button in the pop up to show more information about the POI

For sprint 1 we must be able to select a POI as destination. Just the button is sufficient, implementation is not required yet, all we need is a confirmation we have chosen the POI as destination point

Temporary fix: do not update and keep 23.1.1

Error Message: Content has view with id attribute 'R.id.list container' that is not a ViewGroup class preferencefragmentCompat

Disable the "Go To destination" button instead of having a toast message when user tries to navigate to his current location.

We need to remove html scripts from the descriptions

Given that I am at node 0 and want to go to node 3 and that the path is [0,1,2,3]
If I take the wrong direction and that I reach first a node that is not on the path, then the path is no more valid and is not shown on the map no more.

We have to make sure the path remains valid whenever we reach a POI, and update it if necessary

When the popup for a POI goes beyond the bounds of the image, a part of it is cut off as the webview aligns itself with the image

MAPX390-74