Florian Rival
Florian Rival
Nice thanks for the other tests :) Are we now covering: - Extension renaming - Function renaming - Parameter move for the new ExpressionAndCondition ? Maybe we should have this...
I'm not sure but intuitively it would be better to have these operator and operands parameter at a fixed place, at the beginning just after the "context" parameters, to avoid...
Can you please report this on the forum so that other members can see with you if you're not missing a setting (coordinates not rounded, texture smoothed, antialiasing activated in...
Right, we really need a rework of these namings 😅 What about "Resume" or "Continue"? Would that be understandable?
Right! The question is now, should we favor "string" (which is the "programming" term, also used in the expression like VariableString or ToString), or should we favor "text" (which is...
Sounds better indeed!
Maybe for actions and conditions titles, we can actually write both: "String (text)", "String (text) of a scene variable"... Could make things both exact (string is the proper term to...
> To remain consistent, either all of those would need to be changed, or at the very least, it should read "Text (string)". The idea was to change everything, not...
Would this work with object picking? I guess this could but this would only work for conditions put *after* the "Delete object" action is called (i.e: if you put the...
Hi @eemmaaa, do you remember what you were doing before the bug happened? Thanks!