You are not logged in.

Search results

Search results 1-20 of 65.

Tuesday, March 3rd 2020, 10:45pm

Author: bhh

iPad Pro returning 0 for device.iosversion

Quoted from "klaus.krpano" Hi, maybe your iPad Safari browser is running in Desktop Mode, in this case there are no information about the iOS version available. But it is possible to check for device.iosdesktop to know if running in that mode. Best regards, Klaus That was it! Thanks. Is there way to determine if the user denied gyro permission? I'd like to tidy up the interface a bit, remove gyro buttons, etc. if so. I didn't see gyro2 functions that look like they would provide this info but I...

Tuesday, March 3rd 2020, 6:37pm

Author: bhh

iPad Pro returning 0 for device.iosversion

This was implemented back at 13.1 to open a dialog allowing for the user to request gyro permission. Now on iOS 13.3.1, the iPad is returning 0 for the device.iosversion while my iPhone 10 is returning the correct version. Its really weird, anyone else run into this?

Tuesday, February 25th 2020, 9:00pm

Author: bhh

broken css3d rendering with chrome?

We've got a plugin that basically animates (pulses) some SVG graphics and renders them with css3d as clickable hotspots. I just noticed that it is no longer animates in the current chrome version but does in firefox as well as an older chromium browser we have around. We use the same plugin to do the same with regular plan/map spots and they still works fine. Is there another renderer available to us now we should be using that can render/animate these SVG graphics as a hotspot in chrome or do w...

Wednesday, December 18th 2019, 10:21pm

Author: bhh

ios 13 and DeviceOrientationEvent.requestPermission

Can anyone confirm that this fix requires a button click or user interaction to trigger the request permission dialog? We've got a few projects that are running on an iPad specifically for the gyro control so I was enabling it automatically at startup. I'm now attempting to trigger the permission dialog at startup and I can't seem to get it to fire without linking it to a button. Works fine on a button click (yes, https). Is there an undocumented function call we can make to the new gyro plugin ...

Thursday, July 18th 2019, 11:19pm

Author: bhh

Krpano updates, future and your thoughts?

We'd pay for a subscription as well, or at least an upgrade fee for major releases

Tuesday, May 14th 2019, 8:36pm

Author: bhh

No cursor on a container layer?

Ah, cool. Thanks! I was getting ready to write a "plugin" just to drop a div I knew the name of over the entire screen, lol.

Tuesday, May 14th 2019, 6:35pm

Author: bhh

No cursor on a container layer?

I'm familiar with setting cursors.standard to none and that works brilliant on the actual pano but I need to remove the cursor over container layer that is still able to capture an onclick event so setting bgapture to false is not a viable solution either. Setting layer handcursor to false still has the default arrow. This seems like it should be easy but I'm having a brain fart and have been hung up on this for two days now. Is there a way to assign a class name or id to a container layer so we...

Thursday, April 18th 2019, 4:19pm

Author: bhh

accelerometer/gyroscope sensor access disabled -> will Cardboard VR still work on iOS 12.2?

We use Let's Encrypt. It's free and a legit 3rd party provider so it doesn't trigger browser warnings like self-signed certs will.

Tuesday, April 9th 2019, 6:34pm

Author: bhh

accelerometer/gyroscope sensor access disabled -> will Cardboard VR still work on iOS 12.2?

Also, if you have a previous link saved to the iOS desktop as a "web app" with an http url, you will need to recreate that from a new safari page even with https redirects enabled.

Wednesday, March 6th 2019, 4:43pm

Author: bhh

How are you guys dealing with new iPhone "Home Button" bar?

Hi Klaus, Yea, I experimented with that yesterday. It's pretty cool but my problem with the current implementation of the safearea_insets is that both sides are the same when the phone is horizontal regardless of which side the notch is on. This leads to an awkward layout aesthetically when side-justified UI elements are on the opposite side as the notch where the space is uncomfortably large. It looks good and makes sense when the notch is on the side with the UI but not the reverse. I suspect ...

Tuesday, March 5th 2019, 4:06pm

Author: bhh

How are you guys dealing with new iPhone "Home Button" bar?

The top and bottom bars are indeed huge on both Safari and Chrome on these phones but I'm not exactly sure what you mean by having tabs open. Can you elaborate? I'm using an XR and not sure what you are referring to as the tabs. You probably know this already but if not, the best way to get "full-screen" is to launch in Safari and then Add to Home Screen. Besides looking like a native app, launching from there loses the regular browser navigation bars.

Monday, March 4th 2019, 11:27pm

Author: bhh

How are you guys dealing with new iPhone "Home Button" bar?

We've moved our toolbar off to the side so that isn't a problem specifically but we have project logos that live in the lower corner and it looks pretty bad actually with the phone is in portrait mode. I think a bottom, center justified toolbar probably looks OK as long as there is enough padding off the bottom. If there is a way to detect these specific devices, it may be worth adding a 10 or so extra pixels to anything along the bottom to give it a bit more breathing room. I need to do some te...

Monday, March 4th 2019, 9:54pm

Author: bhh

How are you guys dealing with new iPhone "Home Button" bar?

Just got a new iphone and don't like the way the new bar that replaced the home button that floats at the bottom of the screen collides with the layout of our tour UI. I was curious how you guys are dealing with it?

Tuesday, January 29th 2019, 10:27pm

Author: bhh

Krpano and Progressive Web Apps

agreed. This is pretty cool, thank you.

Thursday, January 24th 2019, 10:54pm

Author: bhh

Custom layer alignments?

Pur, Thanks for posting. That works zooming in on a pano image but it has no affect for me on a regular image layer. Perhaps I'm missing something? There may be an easier way but San7's solution I think is going to work in theory, I'm just having to reverse engineer how to apply that concept to recentering a scroll area since my zooms are just scaling up scroll area inside of a fixed window. It is making my head hurt but I think I will eventually work it out!

Thursday, January 24th 2019, 9:20pm

Author: bhh

Custom layer alignments?

Also, Is the Scroll Area plugin's update() function broken? Seems to be triggering a WARNING: Unknown action error. EDIT: updatepos() seems to be working.

Thursday, January 24th 2019, 4:47pm

Author: bhh

Custom layer alignments?

Thanks San7. Not sure how I missed that the first time around! I see what you are doing, pretty clever. When I first tested, It was only working with the mouse zoom and not with touch but I see why when I looked at your xml file. I'm going to spend some time today working on this and and see what I can come up with along the lines of what you are doing. My application is a little different because my image file is nested in a "scroll area" plugin layer so my "image_onmousewheel" action is scalin...

Wednesday, January 23rd 2019, 7:36pm

Author: bhh

Custom layer alignments?

I've implemented a touch zoomable and touch panable layer (floorplan) via a combination of the scroll area plugin and the mouse zoom hijack trick Klaus illustrated in this thread... https://krpano.com/forum/wbb/index.php?p…touch#post72147 It works great and has a very native OS feel with the exception that zoom events take place around the layer alignment rather than the cursor/touch location. My idea for a solution is to track the cursor/touch locations of that layer and just offset the alignme...

Tuesday, November 6th 2018, 11:27pm

Author: bhh

Chrome 70.0.3538.77 breaks KRPano touch functionality

You rock man. Thank you! Quoted from "klaus.krpano" Hi, this is the reason: https://www.chromestatus.com/feature/4764225348042752 In the next krpano release this change will be included/respected. A workaround for the moment is possible - add these lines in the html file just before the embedpano() call: Source code 1 2 3 navigator.pointerEnabled = navigator.maxTouchPoints > 0; // Edge 17 touch support workaround document.documentElement.ontouchstart = navigator.maxTouchPoints > 0; // Chrome 70 ...