Hi - for Mark and anyone else who was having problems with the displayed
icons.
I've created another layout set, this time with icons 300 pixels in size -
previous set had 500px. This set is visible when you carry out the search
for layouts from the app (settings / button presets / green cross top
right). Having tried it on my phone I think it displays better than the
original 500px set, and it will probably be the set that I go with when I
set as standard.
If possible I'd like to end up with only one icon size and one set
published, otherwise I'm in danger of making a mistake and having slightly
different buttons on each - but if there is a reason for more than one set,
I'll do my best.
Please get back to me Mark, and anyone else having problems with the icon
size - I'm no programmer, but I do have a couple of things more that I
could try that might help.
Regards
Nick
OSM = Tallguy
& Rob - I'd been using the old deprecated version for years, and only
stumbled across the new version by accident - it seems very strange to have
the two.
-- Forwarded message -
From: Rob Nickerson
Date: Sat, 17 Aug 2019 at 23:33
Subject: Re: [Talk-GB] OSMTracker for Android - detailed survey of paths &
tracks layout
To: Andy Townsend
Cc: Talk-GB
Sure I get that from a code point of view, although I was surprised Google
allowed 2 almost identical versions (name and logo) on the store.
Personally I was coming from a marketing and user friendliness point of
view. It's confusing for users and will probably cost the new developer
time in the long run as he/she will probably get some issues raised on
GitHub that relate to the "other" OSM Tracker.
Would have thought a rebrand would have been useful if no way to get the
old app down. Likewise I would have thought a few minutes to make the app
look more maintained on the OSM wiki (e.g. update screenshots, removal of
PDA survey) would of been a help to attract new users.
Anyway, not an issue for me (as I don't use it) so I won't loose any sleep
over this one. Certainly not "upset" just confused by the situation.
*Rob*
On Sat, 17 Aug 2019 at 12:45, Andy Townsend wrote:
> > Why on earth are there 2 versions of OSMTracker for Android on the Play
> store?!
>
> It's open source software, so it's fairly technically straightforward to
> "clone, modify and resubmit". What restrictions Google put on this sort of
> thing currently I don't know, but I suspect they're mostly limited to an
> API usage check and a " dodgy code behaviour" check (that'd be the case for
> an Enterprise Play Store submission).
>
> > Which is the right one and how to get an old one removed?
>
> Maybe there isn't one "right one" ? My recollection was that there was a
> problem with OSM-hosted tile usage in one of the versions (which may have
> been since resolved) and there was a bit of a delay getting it fxed.
> Perhaps someone fixed it in "another" version in the meantime?
>
> Whatever it is, I'd suggest that the best place to ask the question would
> be to the relevant app authors via the Play Store support link, or github
> (at least one of them has a public issues list there).
>
> Best Regards,
>
> Andy
>
>
> ___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb
___
Talk-GB mailing list
Talk-GB@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-gb
