add backdrop - strange problem with scrolling

[Quinto]

Hello,

what would i do:
-create active at mouse position
-add backdrop obstacle at actives position
-change actives animation

When actives animation is finished:
-destroy backdrop at actives position (bounding box)
-destroy active


In frames who does no scroll this works fine!


What happens in side scrolling frames?
-NO backdrop is destroyed when frame is scrolled about 1 pixel or more.
(So it seems to be a problem with the coordinates handled by mmf.)

And yes, the solution who is almost working is:
[color:#009900]-if backdrop is deleted at x("active")- x(left visible frame)[/color]

BUT:
-sometimes the backdrop is visible but inactive and will be deleted
when scrolling out of frame (redraw problem?)
-sometimes the backdrop is invisible but player collides with it
-always all non deleted backdrops will be destroyed if the next active object
has the "animation finished" condition
and starts a new "delete backdrop" action, even if not at backdrops position

________________________________________________
active properties:
-follow frame
-dont inactivate nor destroy if out of frame

frame properies:
-only 1 layer
-max objects: 10000
The number of all object is never higher than 2000.

mmf version: mmf2 dev build 245
________________________________________________




Is this a known bug or exist a workaround for this?

Thanks,
Quinto

[Joshtek]

Have you tried with build 246? One of the bugs it is reported to fix is:

- Runtime : Delete Backdrop At function not working properly in scrolling applications.

[Quinto]

Oh, i didn't see that - had still build 245...

The workaround with x(active)-x(left visible frame)
correctly doesn't work anymore in 246.

But the bug with non deleted or obstacling invisible backgounds is still alive.

Maybe a bug of me? I'll check the code again...

[Quinto]

With manually created and deleted (while mouse key is pressed) backgrounds all is OK,
but i have some loops in the code to create lines of backdrops,
maybe there is the error...