scrolling and button problem

Hi,
I have a scrolling game that uses an active object (a "try again" button) to restart the frame when you fail. This "try again" button only becomes visible when you fail and you can only click it when it's visible. The button only works prior to scrolling. Once scrolling has occurred the button stops working. It is still visible and still positioned correctly but nothing happens when you click it. Any ideas? It is a very simple event and I can think of no reason why scrolling would alter its function. The problem only happens in the iOS build. The button works perfectly when testing in Fusion 2.5. Thanks,
Brett

Do you use the button coordinates to check the click?

I think I have the same issue as Brett. Objects that are set to not scroll (either by being on a layer with "0" scrolling coefficient, or by being set to follow the frame) visibly stay in the same place, but the place were you actually need to touch it with your finger still moves with everything else (meaning the "touch location" eventually goes off the screen).

Brett, try touching the button where it would be if it was supposed to scroll about a second after scrolling starts (for instance, if your screen scrolls to the right, touch just to the left of the button) and see if it triggers. In my app, the longer the scrolling goes, the further away the "touch location" is, until it eventually goes off the screen.

Agree this only happens in iOS devices. Works fine within Fusion 2.5.

Hi aec1525,
I think this is what I'm experiencing. Is there a way to fix this? Thanks,
Brett

Clickteam is already working to fix this bug, I think an update will be released soon.

You can try to disable 'follow the frame of the button' and set "1" to the layer scrolling coefficient

Hi mcm85,
Thanks for the info. How do you set the layer scrolling coefficient? I've never had to do that before. Thanks,
Brett

HTTP://edilcasa.eu/public/Sett.gif

That might work as an alternative method. I haven't tried because I have too many components that I would have to change. My solution is to wait for the bug to be fixed or roll back to MMF 2.0 in the meantime.

Btw, I had a typo in my original post. I meant to say "or by being set to *not* follow the frame".

I tried it.
It worked for me.

It appears that I already have the properties set this way but it did not work. I may try to build again because I updated my iOS exporter. Hopefully it will work. Thanks,
Brett