—

rex_csv2array plugin worked fine in my test in c3 (c3p). Please provide a very simple test c3p file to reproduce your issue, thanks.

I did not find this c3p file. I am looking for a simple example how to use your plugin to read a .CSV file and set to array. thank you!

FYI, for others with my issue, there is a new feature in the latest (stable) release "Wait for previous actions to complete." Not sure how it interacts with various parallal processes (e.g. tween) but hopeful this is a useful new tool. Looking forward to trying it.

FYI, for others with my issue, there is a new feature in the latest (stable) release "Wait for previous actions to complete." Not sure how it interacts with various parallal processes (e.g. tween) but hopeful this is a useful new tool. Looking forward to trying it.

oops. I edited original to include josh at whitkin dot com

I'm interested in developing playable ads too. Maybe we can help each other? Happy to chat - josh at whitkin dot com.

What is your email, skype, website, etc?

Did you find help? I can help.

I've got a line of cards in a family, and they move every few seconds. As they go away, I'd like the remaining cards to move a little to fill the gaps.

Is there any way to call the "arrange/space/vertical" ability that I can do in the layout right-click, but as an action ?

I think the dt countdown hassle is what I really need, and wait is seductively simple but ultimately not the right solution.

I FINALLY found a deep official discussion of wait:

construct.net/en/tutorials/how-to-use-the-system-wait-action-63

Here's a sample:

"The Wait action saves which objects are picked and cancels the current event. When the wait time has expired or it is signalled, the picked objects are restored as they were when the wait started (minus any objects that got destroyed), and the event is resumed from the action following the wait action. It continues to run any subevents as well. At any point if another wait action is encountered, the same save-picked-objects-and-wait process happens, so you can make different parts of an event run at different times."

Big ups for replying in detail! I'm ...kinda...getting it...

DL;DR

Q: I want a sequential conditional ( if/then/else structure) that runs slowly (2 seconds between conditions) so the player can see if/else block execute.

A: For if/then/else, use sub-events, nested elses. to slow it, make each sub-event set a variable and add conditions to nested levels that check it. If you want real-time, set and compare using the system clock ('it's been 2 seconds since the last action ran').

I just made up most of those words in that last sentence. Are there standard terms I should have used?

DETAIL:

Regarding wait: "The whole function is executed in one tick, but some actions from it are scheduled to run later. "

Gah! So confusing for me! It feels like it breaks the "everything is sequential" idea that Ashley stated in an earlier reply to this thread.

Is wait the only action that does this? Does it work like tween does?

Is there a list of actions that do and don't complete somewhere in the docs?

So, now I'm wondering if it's possible to create new action. I'll call it a 'delay' function. Like wait, but makes Construct run the next action once the timer completes.

Why? So I can do what I was tyring to do with wait: create a sequence of actions, and they will happen slowly, one after the other, in the same indentation block, instead of a very deep nest of sub-sub-sub events.

I'm not asking for single-threaded wait - I understand that would freeze Construct.

1. My 'delay' runs the next CONDITION, where 'wait' runs the next ACTION

2. My 'delay' restores execution in the middle of a list of actions, where 'wait' skips ahead.

How? Uhhh... naively I imagine it would make Construct push its position and pick list in the current indentation block. Then it'd break out of the block and execute the next condition, and keep running. Once the delay timer finished, Construct returns to the incomplete block, restores the pick list, and executes the next action after the delay.

yeah, that may not make sense...maybe you advanced coders can help me grasp this.