zenox98

Would you please help me to move this thread into "completed addons"?

shalmu

Moreover, designer could try to extract the logic model from events into plugins. Then he might create another kind of "language" (Domain-Specific Language) for a specific application. Finally the events will be very elegant when reorganize by these new plugins.

shalmu

Yes, I am very sure I am answering your question-

[quote:ebwlz5z5]Are there "Event Smell", like we have "code smells" in programming?

"Condition: Every tick" is similar with global variable. They could be ran (every tick event) or access (global variable) every time or everywhere.

For example. the project has 10 event sheets, each 1 event sheet has 10 "every tick" event. Designer need to check all of these 100 events very carefully when debugging, since they could be ran every tick.

Since there are a lot of non-programmer background designesr, I only could give this suggestion for them. Other topics like re-factory events into functions or using fsm ( I had made a fsm plugin ) might not be easy for them.

If you are a programmer already, try to encapsulate events like in the text code.

( Unfortunately events could not be exported/imported between projects, hope C3 could have this feature. )

Rexu

I could not reproduce this bug, dragging works fine in my test. Could you provide another simple test case?

BTW, tag text was updated. I had fixed a bug while drawing text in canvas2d mode.

I only could tell that : using "condition: every tick" very carefully ( the less the better )

I believe that there is no such feature in current version of C2.

This plugin had been removed. Please contact to official Live2D.

I had made another behavior of simplex noise. It looks like an irregular sine wave.

Update

Fix bug while run "Move approach to" action on staggered board -- test capx

—

Thanks for testing.

Update

Fix bug of getting text width.

Update

Fix bug of getting text width.

Rexu

Thanks for pointing this bug again.

pirx

Method A.

... -> Action:Load all queried items -> Condition:On received -> (Condition:For each item , Expression:CurItemContent) , or Expression:Index2ItemContent, or Expression:ItemsToJSON (for all items)

This flow will read queried items back, a snapshot of these items.

Method B.

Action:Load by itemID -> Condition:On load by itemID -> ( Expression:LastFetchedItemID , Expression:LastFetchedItemContent )

It is another way to read single item from parse server, a snapshot of one item. The received item will not be put into the result of Method A.