08-26-2024 06:35 AM
This is a (dirty) way to get only the index of the changed cluster element:
Not sure why that's useful, but 😁 it sure would be efficient, esp. for large arrays...
08-26-2024 09:07 AM
Interesting loop, a while loop that self identifies as a for loop.
08-26-2024 09:11 AM - edited 08-26-2024 09:11 AM
@LVNinja wrote:
Interesting loop, a while loop that self identifies as a for loop.
Or rather a for loop that identifies as a while loop.
I really love that method actually! I think it can be programmed faster than the while loop.
08-26-2024 09:34 AM
@UnholyPenguin wrote:
@LVNinja wrote:
Interesting loop, a while loop that self identifies as a for loop.
Or rather a for loop that identifies as a while loop.
I really love that method actually! I think it can be programmed faster than the while loop.
More importantly: the result is less and cleaner code.
Consider that a while loop will always executes at least once... So you're always stuck with either a case to skip the action, or a redundant action.
08-26-2024 12:23 PM
@LVNinja wrote:
Interesting loop, a while loop that self identifies as a for loop.
More importantly, the FOR loop will also stop when it runs out of elements. A while loop requires more condition here
08-27-2024 05:28 AM
wiebe@CARYA wrote:
This is a (dirty) way to get only the index of the changed cluster element:
Not sure why that's useful, but 😁 it sure would be efficient, esp. for large arrays...
Have used this one before. Is less janky and weird as it first feels.
You can also get the name of the control which has changed via property node, just make sure to uncheck the "Block UI thread while handling Events" or whatever that terrible default option of the Event Structure is called.....