duplicate of

please delete this thread.

I'll just shamelessly post a citation of myself here:

try to extract the .capx with a decompressing application like 7-Zip and open the included .caproj.

R0J0hound

korbaach

got another issue.

Thanks to you two, my project advanced and I now need to dismember bodyparts (god that sounds harsh).

That's what I got so far: (not very much since I don't want to continue before I got this solved)

Main event sheet:

included event sheet "puppet control":

The dismembering doesn't work when using the disabled event, but when I use the event below that.

(The layout definitely isn't the issue since it stays the same no matter whether it works or not)

I'd like to have all joints-creating events going from the body to the body part.

But apparently, that doesn't work, it just works when it starts at the body part.

Which is weird since the event "Remove all joints", according to its description, is supposed to remove all joints "from or to" the object.

Maybe a bug?

So, there are two main possibilities:

one is with using a 9patch.

one is with using three sprites.

both have advantages and disadvantages.

9patch:

• just one object to manage, better performance with more objects
• can't rotate, only dragging in one direction

three sprites:

• able to rotate
• three sprites, worse performance with many objects

Here is a .capx demonstrating both possibilities:

Download .capx

(enable or disable the group you wanna test. only have one group at a time enabled!!)

Magistross

to much math for me, I'm outta here.

Anyways, thanks for explaining.

Um. Doesn't the events I posted do exactly that?

Or, if not, could you specify what you mean by scroll on a sinus path?

Updated my original .capx post.

You can now scroll the chat while restricting the scrolling intelligently to specific scenarios (see comments in .capx)

This version logs messages to a dictionary but the history of the chat only goes as far as the layout's "margin" setting is set.

I could include a "load from dictionary" when the user tries to look at messages that are longer past than the margin goes.

But that would be a hell of work.

I won't try to replicate a full messenger here. If you want to, go ahead, but I'd say this is quite a base to start from.

With a margin of 2000, this version will be able to save around 100 one-line messages.

I don't know how much a higher margin (i.e. more objects being in the layout but not on screen) affect the performance, but that's to you to figure out.

If you are using only one layer, you can use the system action "Set layer scale".

If you are using more than one layer, you can use the system action "Set layout scale" for your current layout.

So you want to have the text moving up and down (using sine) while moving it from the right to the left?

Add a "Sine" behaviour to the text, set movement to vertical.

Adjust every other value to your liking.

Magistross why can't you just use abs(Sine.Value) and double the interval?

jeffige

Cojoyo

I just realized that there is a possibility which is way easier:

conditions:

• [family] Is on screen (invert condition)
• Trigger once while true
• event:
  • [family] Destroy

Simply give it the behaviour destroy outside layout.

If your window is smaller than your layout and that doesn't work for you, do the following:

• add a family with all the objects you want to be affected by this
• add two conditions:
  • if [family] x is between 0 and Window.width (invert condition)
  • if [family] y is between 0 and Window.height (invert condition)
• under those conditions, add: [family]: destroy