Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - arthur

#1
GENERAL / Re: El regreso (the come back)
November 18, 2015, 06:13:24 PM
Hurray. It's good to see you're back.
#2
MEJORAS/NEW FEATURES / Re: Time in dashboard and TC
November 03, 2014, 04:55:12 PM
If working on the TC could you also enable coordinates in OSGB format to be added as a field.
#3
BETAS / Re: New BETA 5.5.17!
March 01, 2014, 09:42:23 PM
Beta 3 works well for me.



One thought is that when manually switching maps it would be good if oruxmaps kept the true scale constant even if the maps had different zoom levels.



For example suppose oruxmaps was displaying map A (on zoom level 14 and digital zoom 150). Then suppose we manually switch to map B which has no zoom level 14 but has a zoom level 13. Then on switch it would be good if oruxmaps showed map B on zoom level 13 with digital zoom now 300 to keep the scale constant. This would be useful when comparing the same ground features in different maps (with layers of different zoom levels).
#4
A couple of suggested new features, which I think should be relatively minor:



1) Under the "autoscroll delay(sec)" configuration allow an option(s) of less than 10s e.g. 3s.



2) Include the map orientation button as one of the custom buttons - which when pressed opens the "Map orientation" selection. (Ideally I would like a button that toggles between just two map orientations - "oriented by compass" and "Map North Up". However that is maybe a rather specific request.)
#5
QuoteYes, I have to find a solution for different coordinates to lat / lon.


That would be great.



The OSGB uses 3 main forms, being


[list=1]
    • 10 digits - 2 letters followed by 10 digits e.g. NT 25113 73504 - precision is 1m
    • 8 digits - 2 letters followed by 8 digits e.g. NT 2511 7350 - precision is 10m
    • 6 digits - 2 letters followed by 6 digits e.g. NT 251 725 - precision is 100m


    The first 2 letters give a grid box, the digits are then in two blocks the first being the x-coordinate and the next being the y-coordinate.



    To fit the OSGB reference into oruxmaps single length fields you could put the grid box plus the x-coordinate in the longitude field and the y-coordinate in the latitude field.



    Ideally you would give a choice for the number of digits so if someone chose OSGB 8 digit you would show, for example: longitude= "NT 2511", latitude = "7350". (Without a choice of the number of digits, and assuming you keep with the 10 digit form, you would show longitude ="NT 25113", latitude = "73504".)



    Regards,
  • #6
    BETAS / Re: New BETA 5.5.17!
    February 28, 2014, 10:26:39 AM
    Beta2 works well for me. The new zooming and rotation is very smooth.



    (I notice the point Legend makes about the thickness of tracks.



    Regarding the amount of zoom with the volume keys, I think the default of a doubling on each press is about right if, like me, your maps have a lot of layers. However I can imagine that others would want a lower amount of zoom with each press. Maybe the amount of zoom with each key press can be a parameter.)



    Regards
    #7
    Hi,



    I now understand from seeing the new beta that double length fields are not permitted in the radar fields, which is why I could not see coordinates in OSGB format before.



    However the problem is that the single length position fields (i.e. latitude and longitude) do not change format. They stay as degrees even if the units chosen for position is OSGB. Would it be possible to have the unit choice apply to all the coordinate fields? (There are times, e.g. bright sunlight, when it would be very useful having the OSGB position in large characters as would be the case if it could be shown in the latitude and longitude radar fields.)



    Thanks.
    #8
    BETAS / Re: New BETA 5.5.17!
    February 26, 2014, 10:43:15 PM
    Thanks for fixing.



    (Just to echo the previous posts, that the pinch to zoom seems to be fully working with the beta1, and I agree it works well with missing layers e.g. if map has some zoom levels missing. Similarly scrolling out of map range (where not all layers have the same coverage) seems to be fine.



    One point is that it would be very good if the volume key "combined zoom" worked exactly like the pinch to zoom with a constant increment, e.g. 25%, added or subtracted with each volume key press. In other words with automatic movement between layers while keeping the zoom rate constant. Not sure if this is feasible.)
    #9
    BETAS / Re: New BETA 5.5.17!
    February 26, 2014, 01:46:17 PM
    I am trying the new zoom feature and when there is only the one map (with many layers) it seems to work as expected.



    However when I have two maps - one with one layer at zoom 14 and the other with many layers (zoom 6 - 13) - it seems to do odd things when zooming from levels 13 to 14 and back again. (I have "zoom autoload" ticked.)



    For example when pinching in (in other words zooming out) the map will go from zoom 14, 57% to zoom 13, 221%. I would expect the map to switch to layer zoom 13 but with a percentage less than 114%.
    #10
    Hi,



    Thanks for the reply but I don't understand it.



    I am not sure what you mean by double size controls. As far as I am aware I am using normal controls.



    Is there any way of making the OSGB coordinate appear on the trip computer view? Have I some setting wrong?



    Thanks
    #11
    ERRORES/BUGS / UK coordinate does not fit in radar field
    February 18, 2014, 09:18:20 PM
    There appears to be a bug that prevents a UK OSGB coordinate fully appearing in a trip computer field. The last five characters are missing and replaced with three dots.



    If it is difficult fitting the full 10 characters into one field, could you create 2 fields, one for the latitude and another for altitude (but in OSGB notation and not degrees.)



    If a screenshot would help illustrate the problem I could send one.