aelatgt / argon-sdk Goto Github PK

The situation now is that I have two panos (one is with 512 pngs and one is with 1024). They are here:

artnotart.org/jdbolter/argon2test/pere512/Pere512.html
artnotart.org/jdbolter/argon2test/pere1024/Pere1024.html

I have tested both on my iPhone5. Both work.

On my iPad2: 512 works, but 1024 does not ever seem to load.

I am wondering whether there may be multiple camera calibration (FOV?) issues. Here are two examples:

1. This panorama (http://artnotart.org/jdbolter/argon2test/pere2/Pere-Holocaust_2.html) appears much too close in the iPhone5. It is better in the iPad2.
2. This Argon channel (http://artnotart.org/jdbolter/argon2test/placemark-div-multiple.html) is supposed to set up three placemarks in front of the user at a z indiex of -1000, -1500, and -2000 (in other words, 10 meters, 15 meters and 20 meters, right?). On the iPhone 5 the images appear rather close but at least a reasonable distance. on the iPad2, they are practically right on the user with very little spacing at all.

It is funny to me that the problem seems reversed in the two instances, but it must have something to do with the skybox in the one case?

This pano does not work on the iphone 5 or ipad 2. At least not regularly. I believe it worked once on the iPhone5 but not again. The images are right, I think.

http://artnotart.org/jdbolter/argon2test/pere2/Pere-Holocaust_2.html

This code places two buttons on the screen

argon2://artnotart.org/jdbolter/db/doobpano3-argon.html

The button positions is defined in the style #menu as 200px from the left and the bottom. But the buttons may wander or be off the screen entirely. On my iphone5 I found them under the top bar or I guess somewhat above the top. On the iPad2 they usually appear when I would expect, but sometime they wander later.

Students hvae similar problems positioning buttons.

I have been using an iPad for development, and recently started using an iPhone.

compared to the iPhone, i have noticed that for some reason the iPad version is crashing very frequently

Certain webpages fail to close when the close button is hit.

On iPad 4, closing the final (or only) loaded page causes application crash almost every time.

x-frame-options is currently unsupported - URLs that have the x-frame-options header need to be loaded in a separate webview as they can not be loaded into an iframe per the specification

There are certain scenarios that could be enabled by allowing for overriding of GPS location by clients <for example, this allows them to perform local calculations to, perhaps increase resilience to GPS jitter>. This is based on our discussion with Prof. MacIntyre, and is mainly a tracking item for some release down the line.

Unfortunately, this bug does not happen every time. But in the following conditions it occurs about 50% of the time:

1. using iPhone5 on good wifi
2. using the argon2:// access from a note file
3. this link (which consists a panorama itself using images) argon2://artnotart.org/jdbolter/doobpano/pano-argon.html
4. the channel launches, waits and then displays on of the pano images upside and frozen. (oops, it says browser does not support image attachments - I will mail Hafez the image)
5. sometimes the panorama launches normally, although it seems slow.

I have had this freezing happen under other circumstances too, I believe, and at least one student reported it too. Jeff Wilson said he thought it might be a condition of something not being loaded in time when Argon is launched with the argon2:// method. Not sure if it only happens then.

Larger height values in Ar.GeoObject() specifications render lower.