If I were you I'd have a look at the LiteTween plugin.

Seems to me it could be very usefull in cases like these.

If it's just for eye-candy I would create the arc with the custom movement behaviour.

Create a text-object and make this event:

system on start of layout- set text: 64999966 / 1000000

and see for yourself.

Something like this?

on sprite touched - sprite set opacity to 50

I'm still learning about arrays myself, but I tend to use these kind of conditions:

array - for each xy

system compare : array.curY is 0

system compare : array.curvalue is not 0

• set array2.At(array.curX,array.curY) : 25*Array.curvalue

—

You must be right, I must have serious brain issues.

I come on this forum just about every day trying to help people like you, who don't appreciate me taking the time and or trouble.

I'm not sure I agree with the annoying part yet, but I'm sure you can explain that in greater detail (Or is my brain just too small to understand?)

RamPackWobble

Don't sell yourself short. You come up with example capx's in no time and they are usually spot-on. You might still be discovering new and sometimes better ways to do things, but so is everyone. I really appreciate what you do for this community.

I'm not quite sure what you are trying to do, but would a for each instance work?

for each instance

if size is blahblah

trigger once

Nice picture btw.

If a family has an instance variable each member of the family has the instance variable. you can adress the member directly, but you can also adress the family. so the variable can be different for each member of the family.

Thanks RookieDev

I will be posting the capx's soon, but I really want to make them commented before I do that. Problem is, I've been very busy, so I haven't been able to yet. Will try to get to it inbetween the things that have to be done, sorry for the delay.

So save your capx under a different name and start changing it.

I assure you, if you do it right it will work.

Why should someone else do the work?

I'm not sure what you mean exactly by simulating being lifted and moving..

When should the actual finger start being ignored?

When would the new direction be entered?

BTW: you've got mail.

Could be me, but alertmodetest is 4 on start of layout and it is never set to 2 so the event if alertmodetest=2 will never be triggered, will it?