Can't you just use the wacom as mouse input?

Just tested it on my PC and see no issue..

Draw Example

A Wacom specific plugin for construct should be possible to make as well:

Wacom Javascript for Web examples

Because you use family1 in the action and not Sprite, so if there is a Sprite5 and a Sprite object, Construct2 doesn't know which instance of family1 you mean..

Like I said, if you pick the Sprite-object, this will automatically reference the right Sprite3 and Sprite4, but you are not picking anything in your event..

Well your family contains both a Sprite5 and a Sprite, So setting sprite3 and sprite4 to family1 will set them to either Sprite5 or Sprite..

If you only want to set them to Sprite, use Sprite instead of family..

Or make sure ypu reference the right object..

Being in a container with Sprite automatically the right sprite3 and sprite4 are used when picking sprite..

You want it to fit nicely to the last one, so you should set the position based on boundingboxright of the last one..

you should move relative to the one still within viewport..

If you destroy all instances of sprite, sprite3, sprite4 and sprite5 on start of layout, it works better..

Although I'm not sure what you are trying to achieve..

Could you give an example of your capx/events?

LittleStain, i tried your formula and its not working....what am i doing wrong?

I can't see your link, because of forum restrictions..

I guess you'd like to use a different effect, like tint?

When I built as an Android app the .apk size was like 2meg.

This uses Webview

As Crosswalk 20+ meg. Huge difference.

This uses a built in browser and the browser is what makes the file big..

I don't either as long as I don't run it as an app installed from Google Play.

Even the XDK emulator is reading the local storage properly.

I did notice one thing though, when I built as an Android app the .apk size was like 2meg. As Crosswalk 20+ meg. Huge difference.

It might be an issue with local storage in combination with the webview..

The Crosswalk export should however have no issues, because of the built in Chromium-browser..

Like I said:

If this doesn't help, could you share your capx, for this problem should not exist if your game is set up correctly..

I don't know about cocoon.js the exporter, because it has been depricated for a while now..

If the game is working fullscreen on preview, with all different browser-sizes, it probably is related to that..

If it is, unfortunately, it is not a Construct2 issue..