![]() What’s even stranger is that if you have three buttons with links in doc one, it will randomly choose one of the three links to jump to, it’s not the same every time. If the link in hype doc one is to a hype doc which only contains a number of scenes but no external links, then when doc two loads, it moves to a different scene within that doc (you can see the fade transition just after the doc loads) again without any user interaction. This can only mean that when hype doc two loads (which has the link to hype doc three), the link to hype doc three is loaded (without out anyone pressing the link button). Even though there is no link to hype doc three present in hype doc one. In any of the UIWebView apps, clicking on the button in hype doc one, jumps straight to hype doc three. The second hype doc has a button which links to third hype html doc. That button is just a link to a second hype html doc. So for example, I’ll have a hype doc with nothing at all in it except a single button and a graphic. Clicking on a button in HYPE doc which loads a the url for another HYPE doc does not act as it should. However none of the three UIWebView based kiosk apps have worked with HYPE and all have exactly the same problem. Both WKWebView apps, Kiosk Pro and Xstand work perfectly with HYPE (except that Kiosk Pro currently has an iframes bug and Xstand has been discontinued). I have now tried three kiosk apps which use UIWebView and two which use WKWebView. If they don’t satisfactorily help, then let us know – we do want folks using Hype to have success even if the issue isn’t one we’re responsible for. Also we don’t have much by way of debugging facilities that they will have for testing the app. They may have other users reporting the problem and even be able to suggest a workaround. It loaded for me.Īs I said, I recommend contacting their support since the problem started with an update that they did. I put this on a local server, and set Kisok Pro Lite to use this as a URL. I used as the URL and then exported a basic Hype document. In this manner, I cannot reproduce the problem. In fact, having the working case is also useful for comparison! So it saves a lot of time on both our parts to have the exact reproducible case. The server you choose may be a deciding factor in if it is shown as well. For example, the URL you choose may be a //, or some other protocol URL. We ask for your document because there are a lot of variables that might be done differently that may not have all been tested.
0 Comments
Leave a Reply. |