[Loadstone] Exploration mode

Shawn Kirkpatrick shawn at odyssey.cm.nu
Thu Oct 25 08:34:48 BST 2007

Rob's explanation is pretty much correct. If exploration mode were to be 
related to your current heading you'd get the problem of an unstable map. 
The only thing I can think of that could do this would be if the map could 
be turned in relation to your current heading. There's a couple problems 
with this, when does the turn happen, and then the directional output would 
have to be changed since cardinal directions wouldn't be right anymore. We'd 
need an 8 way directional output system, maybe not that hard to come up 
with. This whole thing would probably have to be another mode or on another 
set of keys if we had them.
There's plans of making the show area function work from navigation mode. 
What points are of interest there would be dependant on the user. Just 
showing the points forward might not be quite what you need if you're 
looking for something in the area. We might be able to make the show area 
work in a given direction but the real problem there is we're simply running 
out of keys to put functions on. Maybe we'll have to resort to long key 
presses and shift long key presses to get everything we want in.

On Thu, 25 Oct 2007, Rob Melchers wrote:

> Ari,
> You are talking about the view angle in both exploration and navigation mode. 
> In exploration mode we are looking at a map, and maps have a tendency to be 
> viewed with the top of the map to the north. Looking to the north (key 2 in 
> exploration mode) from our present point of view LS uses a wide angle, 
> virtually going there and looking south (key 8) the view angle is not 
> changed. This will sometimes result in the effect of not going back to the 
> starting point when jumping from north to south and back. I've tried to 
> eliminate some of this behaviour in the 'Database Explorer' on the tools page 
> by providing adjustable view angles. However, I don't know if the phones we 
> use have the kind of computing power to cope with this extensive sorting of 
> expected points. Again, the clockface approach is a relative approach and 
> does not belong in Exploration mode. It would be like turning the map around 
> all the time. In Navigation mode the clockface announcement is relevant to 
> the users position and movement, because the user changes position relative 
> to the cardinal definitions of the compass. Here also the view angle comes in 
> effect and it would be nice if it could be adjusted (but same arguments as 
> above). Maybe Shawn can shed some light on what view angle is used in both 
> modes. Also, see if the 'Database Explorer' on the tools page gives some 
> hints of how both modes could work on the phone and let us know your 
> findings.
> Rob
> At 10/25/2007, you wrote:
>> Hi Charlie
>> On Tue, 23 Oct 2007, Charlie wrote:
>> >> It would be better if it reported always nearest item in front or
>> >> preferably list of those items. When entering exploration mode LS could
>> >> remember latest valid heading from navigation mode and afterwards use
>> >> heading of latest virtual movement.
>> >
>> > No, in exploration mode the reporting should be absolute.
>>   Is there any other reasons beside complexity of coding vs complexity of
>> usage?
>>   I still remember those text adventures from eighties but do  not want
>> them back. One feature of those was that if user move one step to east and
>> one step to west he/she was not necessarily same place as before those
>> steps. Same applies to LS exploration mode.
>>   If we think a straight road from west to east with four waypoints (A, B,
>> C, D) 100 meters apart each other and one, E, 50 meters north of C.
>>            E
>> A    B    C    D
>>   If we walk physically from west to A  point B is at 12 o'clock. If we
>> turn exploration mode B  is not more in front of us but in the east. Ok...
>> where is east... back to navigation mode, walk a little... ahh, we were
>> walking east  so now we know B is till ahead... oops.... east, not ahead.
>>   If we now move virtually to B, the only visible waypoint in location A we
>> got A in west, not back at 6 o'clock as in navigation mode. C  is at east
>> and E is at east too but non-visible. To 'see' E we have to move virtually
>> at point C and there  instead of turning  left as in real navigation turn
>> to north.
>>   Now comes the funny part. We are at point E. C is at south, At east there
>>   nothing but LS clains there is D. If  we move to E and  'back' to west we
>>   are at point C.
>>   In every movement there were heading: to east when we reached point A,
>> east from A to B and B to C, north from C to E,  something between east
>> and southeast from E to D and west from D to C.
>>   On every location there is also availalbe clockface-type heading to all
>> points. I'll left calculation as an exercise to the reader:-) Tip: at B A
>> is at 6 o'clock, C is at 12 o'clock, D is at 12 o'clock and E is at 11
>> o'clock.
>>   Show area -function is a step to rigth direction but it is buried too
>> deeply in the menues and is available only in exploration mode. It also
>> lacks a important feature to filter out all
>> but  most interesting points, the points  ahead.
>>   > Bert
>> >
>> >
>> You can still escape from the Gates of hell: Use Linux!
>> --
>> mr. M01510
>> _______________________________________________
>> Loadstone mailing list
>> Loadstone at loadstone-gps.com
>> http://www.loadstone-gps.com/mailman/listinfo/loadstone

More information about the Loadstone mailing list