| Commit message (Collapse) | Author | Age | Lines |
... | |
|
|
|
|
| |
If iOS7 set a class on the body and then use this to override various
styles as well as the position of the map
|
| |
|
| |
|
|
|
|
| |
For soft launch strategy
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This helps to stop crashes on Android when taking photos due to out of
memory issues
|
|
|
|
| |
To remove duplication of option setting
|
|
|
|
| |
Mostly to prevent restarts on returning from the camera
|
|
|
|
|
|
|
| |
This means that if something happens to interrupt the reporting process
then any user details entered are not frustrating lost.
Fixes #140
|
|
|
|
|
|
|
|
| |
Only display the cancel button in the toolbar, use a different button
with different text to indicate you are adding a location to an existing
report
Fixes #138
|
|
|
|
| |
Fixes #136
|
|
|
|
| |
Fixes #136
|
| |
|
|
|
|
|
| |
At the moment there's a lot of glitches on Android 2 so initially
restrict to Android 3+ as that seems reasonably stable
|
| |
|
|
|
|
|
| |
Slightly less jarring than a dialog if something goes wrong during app
startup
|
|
|
|
|
| |
It doesn't add anything other than a moment of possibly distorted logo
so we might as well get rid of it
|
|
|
|
|
| |
Otherwise may_show_name is always set to true on server
Fixes #135
|
|
|
|
|
|
|
| |
Stops people who never want to show their name having to click the
option every time.
Fixes #134
|
|
|
|
| |
For consistency
|
| |
|
| |
|
|
|
|
|
|
| |
This is hopefully to fix the rendering issues on the Galaxy S4.
See #116 for details
|
|
|
|
| |
Fixes #132
|
|
|
|
|
|
| |
Just add extra text to the button.
Fixes #131
|
|
|
|
|
|
|
|
| |
Also update it when adding a photo to give an indication that adding the
photo was succesful. This is to remove any confusion about whether the
photo on the page has been added.
Fixes #130
|
|
|
|
|
|
|
|
|
| |
Set Android 2 to use adjustPan when the soft keyboard is visible as this
stops the details screen scrolling in such a way that the cursor is off
the top of the screen. Leave the default for other versions as then
the screen is scrollable.
Fixes #128
|
|
|
|
|
|
|
|
| |
Both by setting the height of the container to 100% so it always covers
the screen and also by adding a transparent background to emphasise that
it's covering the screen.
Fixes #127
|
| |
|
|
|
|
|
|
|
| |
Just to make it obvious you need to click the confirmation link to set
activate the password
Fixes #124
|
|
|
|
|
|
|
| |
Mostly to make the user realise that they need to click the link in the
confirmation email to activate the password.
Fixes #125
|
|
|
|
|
|
|
|
|
|
| |
Overload PinchZoom control to check if we are at the limits of zoom and
if so ignore any pinch zoom that tries to go past those limits. This
stops the visual glitch of the zoom sort of working and then snaping back
and also gives a visual indication of when the zoom limits have been
reached.
Fixes #118
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes #113 in that it means the user can move the screen to see
what fields are available. Previously this was prevented by setting the
adjustPan mode for the soft input mode which had fixed a bug with the
keyboard not dismissing on transition. This has been resolved by adding a
plugin for Android to control display of the soft keyboard and hiding
the keyboard before navigation in the navigate method of FMSView.
Sadly this then meant that the screen size was being measured *before*
the keyboard was dismissed with the result that the screen transitioned
too was incorrectly displayed. This was resolved by taking the screen
height on start up, storing that as a property of the FMS global object
and then using this property instead of measuring the screen size at the
time of transition.
The map has also been expanded to fill the whole screen rather than
stopping at the bottom of the navigation bar as on Android when you
scroll the screen the map does not scroll and the gap at the top was
visible.
|
|
|
|
|
|
|
|
| |
Again, this is to make sure the button is visible when the keyboard is
on the screen. This is at the cost of button placement consistency but
it's probably more obvious of the user.
Related to #120
|
|
|
|
|
|
|
| |
This avoid the big gap in the screen and also means that the button is
visible when the keyboard is on the screen.
Fixes #120
|
| |
|
|
|
|
|
|
|
|
|
| |
This should both stop issues with memory on phones and also reduce
upload size. Will cause upscaling on phones with < 3MP cameras.
3MP picked as a compromise between quality and file size.
Should fix #121
|
|
|
|
| |
Stops it appearing on the screen before the photo and looking odd
|
|
|
|
|
| |
Replace console.log call to a wrapper function that only outputs if
we've set a flag in config.
|
| |
|
|
|
|
|
|
|
|
| |
On the inital screens the android back button should quit the app, or if
on the map screen and you've started a report it should cancel it. Add
in a default back method to FMSView and an override method for the map,
exising report and offline screens
Fixes #117
|
|
|
|
|
|
|
|
|
| |
As the front page only serves to work out what to do on load we should
never set the currentView to front-page. However, due to execution order
what actually happens is that the navigation to the front page completes
after the navigation to the actual page displayed. This means that the
incorrect currentView is set and the easiest way to fix is to prevent
the currentView being set to the front page
|
|
|
|
|
| |
Results in much neater scaling
For #115
|
|
|
|
| |
Fixes #90
|
| |
|
|
|
|
|
|
|
| |
To stop it accidentally being mistaken for the next action button move
the photo button to be a red X button in the lower right corner of the
photo.
Fixes #112
|