Detect Proximity to an object? - From clicked web page back to dimension?

5 views
Skip to first unread message

sware

unread,
Aug 22, 2009, 3:17:23 PM8/22/09
to Gamaray
1. Is there a way to code an object so it cannot be clicked on until
the user is within a certain proximity of the location? (Sorry if
it's in the doc but I'm only seeing the <refreshDistance>
<validWithinRange> tags which seem to be for distance traveled since
last refresh)

I'm developing a test scavenger hunt type thing where I would like the
user to arrive at (or get close) to a location, then be allowed to
click on the object to load another .gddf with the next point to seek.


2. I noticed that if you click on an object in the dimension that
takes you to a website (that is really cool) when you press the back
button it takes you to the previous web page visited which may have
been the html page that brought you to the dimension. At that point
you are forced to reload the dimension. I wonder if there is an
operation that will allow the user to navigate back into the dimension
without having to reselect it from an html page?

An example from the scavenger hunt would be the user clicks on
dimension image, it takes them to a URL with a full screen photo or
additional info about the location they are at, then it would be ideal
if they hit the back button on the phone and it would return them
directly into the dimension.





Clayton Lilly

unread,
Aug 24, 2009, 9:56:17 AM8/24/09
to Gamaray
1) We will be adding an onDistance event to features fairly soon. If
you are working with static dimension XML files, you could have the
features not be click-able in the main dimension XML, but then when
you are close enough (the features onDistance is triggered) you could
load a dimension XML where that feature is click-able (and the next
feature is visible). The scavenger hunt idea sounds really cool.

2) That is an issue. A work around for now would be to put a link in
the photo HTML page that points back to the dimension XML, and ask
users to click that instead of using the back button. Gamaray won't do
a full reload in that case, it should just display the same dimension
right away (if it was the one already loaded). The long term solution
is we need to embed a WebView into our application instead of calling
the external Android web browser. This way the Gamaray client would
have control over all interactions.
Reply all
Reply to author
Forward
0 new messages