You could also do it the opposite way by having an invisible white (or other colored rectangle) the size of the visible screen and have it fade in (giving the impression that the level is fading to the next layout). You could then have any objects that you want visible still moved to the layer above the rectangle.

Excal any chance you can post a sample capx of the solution you came up with for two touch zones? I may have use of it in a future project.

Throws me off at times too, C2 considers the right hand side to be the front of the object...

Not to be rude, but if you can't follow the manual, you may have issues following other descriptions as well. Or do you want someone to do the work for you and just hand you a working solution? If that is the case, there really is no reason to use the tool. And it's not a spontaneous manual, it is the manual for the tool that you are using and the place where all the others here have gotten their information. Manual, then Tutorials, then Experience are usually the three places you get the info. The third one comes much more quickly if you have first properly attended to the first two.

The items that may have a resolution for you are webstorage, the new save system, or JSON calls. Any of those are going to require that you read up on them. When you want your drivers license do they let you say, no I never read the rules, or practiced driving, but I have seen cars on T.V. before so give me my license? It just makes no sense to want to know how to do something without wanting an accurate explanation.

Whiteclaws damn, that gives me a headache lol

Jumpthrough is supposed to act as a solid that you can jump through either up or down. I believe that is the expected behavior. That way the player can still run on the platform once they jump onto it.

I have noticed some oddities with it though, I tend to get a slight invisible ledge just below the edges of my jumpthrough platforms. If the player jumps and just misses the edge of the jumpthrough they tend to float just below it for about half a step, then continue to fall as normal.

Ashley is this expected behavior?

— Makes perfect sense. Sorry if I misunderstood. I do not deny that it would be a useful feature in some scenarios as well.

— I mean during editing the project, not during running of the game. This would be in Construct2 while working on layouts.

Hello Ashley,

I wanted to just put in a request to see if there is any way to update the zoom in/out of the main canvas/layout area to be mouse aware. That way if I have the mouse centered over a particular object and I use the ctrl + scroll it will zoom to the point I am pointing at with my mouse. Otherwise, it tends to take zooming then scrolling, rinse, repeat, to get zoomed in on a particular object. This would be a great time saver when working on large canvases and needing to zoom in on specific objects.

If there is already a method for this, please let me know. Thanks again for all the hard work. The past few months have seen an amazing amount of new features implemented.

California you may want to talk about why you want particular functionality and how it will benefit us instead of just stating that another app does this. That may give them some actual reason to look at implementing a feature.

Squidget I found the same issue, I created a jump animation, and the animation is short as the character should just hold the finishing pose/frame until the jump ends. Instead what happens is that the character freezes in mid-air on the last frame of the animation and the hitbox keeps moving. Once the box hits the ground and the next animation is called, the sprites snap back to it. lucid is this an issue with the plugin?

— It is a large assumption that it has been accepted as a change. Also most likely they already have their goals for the next few releases set. So pushing them to force it into the next update is very unrealistic.

A. Need agreement that it is a workable solution to be implemented

B. Has to fit into a release window that has room for the work required

C. Has to be accepted that this is something that they need to do in the first place.

Until the three of those happen, I would not demand they have it in the next release as it is really up to them on if, when and how it actually happens.

Not trying to be negative, it is just pretty rude to demand of them and assume they are doing what you have instructed. When they look at issues to fix they also have to look at the impact it has on their overall development cycle and any possible impact to the existing code. I would say highly unlikely waiting for the next release is going to help you unless they come back and say oh yes, that is our top priority to do currently.