Custom Essay Writing Service
Essay Writing Services
Custom Essay Writing
Custom term paper writing
Research Paper Writing Services

In fix #2 that I mentioned, we need to remove the ‘else’. Apparently, a lot of flickering appears on iOS when using TOUCH_END instead of MOUSE_UP. While this is strange, fortunately the flickering does not occur when we move our finger through the status bar. So we combine the things that work: adding both listeners makes the scrollview work fine without any flickering and does indeed fix the status bar issue.

By the way… don’t forget to remove the listener in stage_mouseUpHandler().

Great work on this. It comes close to the original UIScrollView already.

I fixed some of your – and my own – issues:

1) To prevent the jitter, replace all instances of ‘e.stageY’ by ‘this.stage.mouseY’. Using trace, I found out that the latter *does* produce correct results. You’ll find the jitter gone.

2) When using this on iOS, you’ll find that when you move your finger over or beyond the status bar, your scrollview does not ‘release’ (i.e. the mouse up event is never fired). You can listen to the TOUCH_END event instead, which *is* fired. Yes, more strangeness. I used the following to still allow testing on the computer:

if( Multitouch.supportsTouchEvents )
stage.addEventListener(TouchEvent.TOUCH_END, stage_mouseUpHandler);
else
stage.addEventListener(MouseEvent.MOUSE_UP, stage_mouseUpHandler);

4) At the start of the this_mouseDownHandler() function, I added something to make sure any existing tweens on the scrollview are stopped immediately:

TweenLite.killTweensOf( this );

5) I set mouseChildren to false only when you start dragging and back to true when you stop. This allows you to have mouseChildren inside the scrollview, should you require them.

6) You can set cacheAsBitmap to true when you start dragging and, optionally, back to false when you stop. This could improve performance while dragging, assuming the scrollview’s content is not changing meanwhile.

7) I increased the DECAY constant to 0.93. Might be a personal preference. xD (Oh, and made it an actual constant rather than variable.)

Let me know if this helps you out. If you have any upgrades, I’d enjoy trying them.

Question:
What is the purpose of e.updateAfterEvent() call? Doesn’t the player update after the frame anyway?

Kind regards,
Timo

Also, iOS skins are now present in the Windows simulator, and OpenFeint is now supported on Android (docs updated as well)

Thanks again for the great article! —Just thought I’d clarify those few points, for you as well as anyone else interested.

The game Psychonauts is a well documented and fairly representative case study using Lua. It had 260,000 lines of C++ and 400,000 lines of Lua. The team had over 40 members, though not all were necessarily coders.

[...]the time to read or visit the content or sites we have linked to below the[...]…

[...]while the sites we link to below are completely unrelated to ours, we think they are worth a read, so have a look[...]…