Missing Composer.* transition effects

Solar2D Composer
#1

There are some missing transition effects that have been bugging me for a long time.

What I want to do:

(a.) Slide a new scene from the bottom over the current scene. I can do this with the “fromBottom” effect.

(b.) Slide the new scene back down revealing the old scene behind it. 

(b.) isn’t possible to do.

The transition effect “fromTop” will slide the “old” scene down from the top. “slideDown” will do the same and also push the other scene down.

Both of these effects are visually incorrect as the old scene is perceived as already being behind the new scene. What is required is to have an effect where the scene being transitioned to is put behind the currently visible scene and then have that scene slide down (or in whichever direction) to reveal the other scene behind.

The only visually acceptable workaround I have at the moment is to do a “crossFade” transition for (b.).

#2

BTW. I know that this can be achieved with the overlay functions, but I’d like to have these effects for normal scenes as well as the hide/show events are not called for the parent scene when using overlays.

#3

try this, vary to suit: [edited to clarify]

composer.effectList["panelDown"] = {   sceneAbove = false,   concurrent = true,   from = {     yStart = 0,     yEnd = display.contentHeight - display.screenOriginY\*2,     transition = easing.outQuad   },   to = { xStart = 0, xEnd = 0,     yStart = 0,     yEnd = 0   } } composer.gotoScene("theOriginalUnderneathScene", {effect="panelDown",time=500})

–

#4

:blink: Did I miss some secret documentation?

It’s fantastic if it’s possible to create custom transitions!

Thanks!

#5

possible=yes, documented=no.  (use legacy storyboard as doc = same)

#6

I tried it and it works. This is great.

Thanks for the tip!

BTW. I dumped the table and out came a bunch of fun stuff  :stuck_out_tongue:

#7

yep, tho silly that we have to “hack” our way into this stuff

wish they’d open-source ALL the lua-based api’s (as they did w widgets 2)

it can be an eye-opener to peruse what’s already been legacy’d (sprite/widget1/storyboard/), pretty easy to spot certain bugs, and there are published apps out there with them!  (myself included - i feel like i need a shower every time i look at the original storyboard source [which i’ve since heavily modifed]).  we need access to fix it ourselves, after all it’s our necks on the line when we publish.

just my two cents

maybe i need a bigger license.  are you, with an enterprise license, provided the lua source for such libs? (or are they provided precompiled)

#8

Nope. No special treatment… I’m out in the cold like everybody else.

#9

BTW. I know that this can be achieved with the overlay functions, but I’d like to have these effects for normal scenes as well as the hide/show events are not called for the parent scene when using overlays.

#10

try this, vary to suit: [edited to clarify]

composer.effectList["panelDown"] = {   sceneAbove = false,   concurrent = true,   from = {     yStart = 0,     yEnd = display.contentHeight - display.screenOriginY\*2,     transition = easing.outQuad   },   to = { xStart = 0, xEnd = 0,     yStart = 0,     yEnd = 0   } } composer.gotoScene("theOriginalUnderneathScene", {effect="panelDown",time=500})

–

#11

:blink: Did I miss some secret documentation?

It’s fantastic if it’s possible to create custom transitions!

Thanks!

#12

possible=yes, documented=no.  (use legacy storyboard as doc = same)

#13

I tried it and it works. This is great.

Thanks for the tip!

BTW. I dumped the table and out came a bunch of fun stuff  :stuck_out_tongue:

#14

yep, tho silly that we have to “hack” our way into this stuff

wish they’d open-source ALL the lua-based api’s (as they did w widgets 2)

it can be an eye-opener to peruse what’s already been legacy’d (sprite/widget1/storyboard/), pretty easy to spot certain bugs, and there are published apps out there with them!  (myself included - i feel like i need a shower every time i look at the original storyboard source [which i’ve since heavily modifed]).  we need access to fix it ourselves, after all it’s our necks on the line when we publish.

just my two cents

maybe i need a bigger license.  are you, with an enterprise license, provided the lua source for such libs? (or are they provided precompiled)

#15

Nope. No special treatment… I’m out in the cold like everybody else.