There is an issue.
I have this formula: N48° 23.044+x

If I put 50 in the field for x than the result is not correct. Coordinate jokes's result is N48° 23.940 but the right result should be N48° 23.094.

So there is an issue if the first number after the dot would be zero.
I hope this could be solved.

Just a first vague idea for better usability now that we have two variables...
Not really sure yet if it really simplifies usability:

IS: Given listing formula like (A+B) * B * B, with B being known (e.g. 7), A unknown, you need to pre-solve the formula for given B or insert B three times

GOAL: What about just taking the formula as it is and selecting letter A range 0-9, letter B range 7 (one single value range), then pressing show button. Letters could be offered in dropdown depending on what is contained in the formula, to keep it faster than entering three times B manually.

I should take care not to destroy functions like exp, abs etc. if letters can be chosen freely instead of just x, y

projection part not considered for detection and replacement yet

Currently the help says you should leave the second variable empty, if the formulas contain only one variable. It would be nice, if this would be detected and be deleted automatically

Often not only one stage/answer is unknown, but two.
It would be fine to have an additional variable, y.
y should have its own range / discrete values.

Waypoints are then generated for all combinations of all x and y values. Of course there must be an upper limit of the number of generated waypoints.

Optional: A third variable z. But this is only seldom necessary!

Example: N 53 08.(850-2*x) for x=380
becomes N 53 08.90
but should become N 53 08.090

limit x-range to avoid getting unreasonably many points

Thx page to all contributors
8jasuli8 for logo design
bubendorf for new features, see #18, #19, parenthesis handling

exceptions already give detailed correction instructions in English

remove unused libs, enable minimization > reduces size to nearly 1/2
adjust open source info to changed libs

Overdraw: Painting regions more than once

If you set a background drawable on a root view, then you should use a custom theme where the theme background is null.

cgeo obviously is offered when no mime type is provided, so add this option to settings and cgeo preset and simplify intro (no need for using a filemanager anymore)

affects version 1.0.9

html input produces N 53° 12.345'\nE 10° 12.345'
The first ' prevents correct parsing.

Solution: Pattern.compile(pattern, Pattern.DOTALL), i.e. dot matches newline too.

autoconfiguration should not be part of intro but of main

Great work on Coordinate Joker, it fits a need I had more than once. Would you mind your app being served through the opensource/free repository f-droid.org? I think the app fits perfectly the f-droid requirements (no closed source dependencies, copyleft licence).

noticed that my edited range was not stored. maybe simply due to the removed finish(), but I had already refactored everything when I realized that :(
Model now holds the raw range definition only and IntegerRange.getValues() now became a static function for on-the-fly string to value list conversion.

when user selected locus or cgeo in quick settings, we should filter for it instead of leaving the intent open to other apps

y seems to be initialized with 0-9 although old formula contains no y

when filling model from UI
observed on Galaxy A3 Android 6.0 on version 1.0.9

See this test as an example:
assertEquals(10.0, Calculator.evaluate("abs(y(x+1))", x:-12, y:1));

The formula evaluates to abs(1(-12+1)) = abs(1-11) = 10

I would rather consider this an error case because -11 has an unary minus which must not be interpreted as a two input minus operator.

The desired behavior would be that such cases result in an exception - maybe later on in ExpressionBuilder's evaluation, e.g. by keeping it abs(1(-11)). That way such points would be sorted out while correct ones will still be calculated.

Probably geocachers won't check beforehand for single digit terms like (x-3) that the input range for x should not start at 0, so this may become relevant in practice.

linebreaks can be entered much easier than °, '

regex ([N,S])([^°])°([^'])'?.([E,W])([^°])°([^']*)'? requires ° in string
Idea is to match xxx m or ft xxx ° TN or vice versa at the end of the string too
Next try without projection, but with °
Next try without °
Next try without ° and without projection
or similar.
So first try is most strict
then some patterns that deliver less results or have higher risk to produce a wrong match. If those later tries produce the correct result, the user is happy, otherwise he can edit it to match the strict format.

I think to have seen multiline extraction results on some device but with alpha 1.2.19 long results instead reached over the right screen end on my device.
To be investigated

nearly no own code in there, except for a looooong GPL string resource ;)

smell: duplicate code

should be done automatically instead: from currentVersion downto previousVersion ignoring non-existent files. Special treatment only for "14_and_before".

adjust to recent changes (range, two variables)

Received user request to add support for "Quersumme", I would then also want to add repeated digit sum, i.e. root sum.

Wenn die gewünschte App dort nicht aufgeführt ist, kannst stattdessen die Experteneinstellungen verwendet werden.
...
Das genau Vorgehen variiert für unterschiedliche Android-Versionen und Varianten.

Example:
N 53 11.(x/4)23 results in N 53 11.0.2523 for x=1
Currently all calculations are stopped and an invalid formula message appears. Obviously this could be avoided by running x=0-36#4 but the app should also work, if the user did not think about valid x values.
Instead such points (like x=1,2,3 in the above example) should simply be omitted, just resulting in a warning, that not all points resulted in valid coordinates.

esp. for non-Locus explain about saving gpx and then opening it

On first startup: if Locus is not found, settings should be initialized for gpx output (and maybe send instead of view action).
This would make it more convenient for c:geo users to get it running without obstacles.

The activities

• help
• terms of service
• privacy policy
• open source licenses

have same layout and similar code, so let them share the same layout and move common code to base class

Often the question in the geocaching listing gives some answers together with a number. So it would be fine if I could enter these discrete numbers instead of the range to be used for x.

Es wäre hilfreich wenn man die Formel als ganzes aus dem Listing kopieren könnte statt einzelner Felder.