Sub-issue #1: I agree the disappearing icons/buttons interfere with map moving actions of the user. How about we have a fixed button on one of the corners, possibly lower ones, of the screen. The button shows always there, but it's not a big button. Also, we could make it optional to the user to have it. In addition, we could have a menu item. Pressing the button or the menu item would open the full screen stats page. What do you think?
Sub-issue #2: do we have to create a service that will maintain the stats or can we do this just by addidng a listener to GPS events, a listener that will update the numbers and exit. Till the next GPS event.
kizza wrote:
> I don't like that the arrows are not a standard Android UI element. They disappear when the map is not being touched so activating the button requires 2 actions. Also, I think the buttons are a bit too small so sometimes I move the map accidentally.
> You've convinced me about the need for full screen though.
Sub-issue #1: I agree the disappearing icons/buttons interfere with map moving actions of the user. How about we have a fixed button on one of the corners, possibly lower ones, of the screen. The button shows always there, but it's not a big button. Also, we could make it optional to the user to have it. In addition, we could have a menu item. Pressing the button or the menu item would open the full screen stats page. What do you think?
Sub-issue #2: do we have to create a service that will maintain the stats or can we do this just by addidng a listener to GPS events, a listener that will update the numbers and exit. Till the next GPS event.
kizza wrote:
> I don't like that the arrows are not a standard Android UI element. They disappear when the map is not being touched so activating the button requires 2 actions. Also, I think the buttons are a bit too small so sometimes I move the map accidentally.
> You've convinced me about the need for full screen though.