Tumult Hype 3.6.2 Released

1

Howdy forum-goers! Hype 3.6.2 is now out and we recommend that everyone upgrade! Please see the blog post for more info:

###Bug Fixes

  • Fixes issue with audio not playing on iOS 10.3 (re-export required!)
  • Corrects issues exporting Animated GIF and PNGs on older versions of macOS
  • Fix issue where Animated GIFs with background transparency could show previous frames
  • Tabs will magnify when mousing over
  • Dragging multiple assets from the Resources Library won’t create extra copies anymore
  • JavaScript API callback for “HypeResourceLoad”

Enjoy!

9 Likes
2

wouldn’t it be straight forward to also return the element(s) along with the url on HypeResourceLoad …

3

How to use the JavaScript API callback for “HypeResourceLoad” ?

4

usage of those custom- event-callbacks in general is part of hypes js-documentation …

 function myCallback(hypeDocument, element, event) {
console.log(hypeDocument);
console.log(element);
console.log(event);
    return false;
  }

  if("HYPE_eventListeners" in window === false) {
    window.HYPE_eventListeners = Array();
  }
  window.HYPE_eventListeners.push({"type":"HypeResourceLoad", "callback":myCallback});
2 Likes
5

YEEESSSS..

Thank you..:smile_cat:

3 Likes
6

I may have named this poorly; it is really more like a "URL construction" callback for resources. It can be called many different times, such as preloading, setting a background-image or video source, AJAX call for WebAudio, etc. Given the variety of ways/times this might be called, I'm not sure how useful the triggering element is. Do you have some example use cases?

Within the myCallback() function @h_classen wrote above, note a few things:

  • event.url is what will be loaded.
  • you can return a string and this will override the URL.
  • it may be called multiple times for the same resource so generally make sure it returns the same URL if you are overriding