Jump to content
Search Community

George

Members
  • Posts

    3
  • Joined

  • Last visited

George's Achievements

1

Reputation

  1. The debug console logs shows TweenLite works everything correctly during my testing tonight with Android tablet when changing fullscreen mode. Switching to fullscreen mode do breaking image loading or off-screen cache so it failed to draw mysteriously, making the game as if 'freeze', even those image data do exist and 'drawing' on canvas. Thanks again for helps. Thanks Jack for making such a great library for AS3 and Javascript.
  2. Thanks for replies. I'll take a look and investigate more later when have time. The problem happened only several times (still several games under development so didn't test too much though) when testing on iphone/android tablet on first touch event. As workaround the first touch would trigger sound for iOS, in Android it would trigger fullscreen mode. Each time this kind of issue happen the game would stop, and it's a moment the game running one or two tweenlite instances (one view tween in another tween out) while at the same time the browser likely interrupt/pause the regular Javascript process, for example, playing the first sound at the first touch in iOS Safari would take a short moment browser 'freeze', touch canvas to switch to full screen mode would 'freeze' the android chrome browser a little more second (all game graphics would be resized to fit for larger screen size at the moment which would cost some Javascript time as well). So I guess this would possibly stop the tweenlite instances because of waiting too long. Tweenlite works quite well if not in these special situations. I'll try to get more debug information later to see where the real problem is.
  3. I'm using GSAP for HTML5 games on mobile devices, it works great so far. One thing I noticed though, when some browser events happen, such as rotating devices which would force screen resizing, or change to fullscreen mode, GSAP tween likely stop working and break the game logic. I did some search someone had similar issue (that case not on mobile though), the workaround was to set a timeout instead of using onComplete function. I'm not quite sure whether GSAP would plan to investigate these issue or not. Thanks
×
×
  • Create New...