BUG?: The NSelectedObjects Function doesn't behave as expected. It only returns a single instance of an object when multiple objects satisfy the new Pick Conditionals.
Example MFA: PickMinMaxValueCountProblem.mfa
While I'm uncertain if this behavior was intentional, ideally I'd want the total number of objects that meet the criteria and I would use the Pick Object at Random in combination if I wanted a single instance.
-oh and now that I think about it is there any reason why we don't have an action to grab the lowest or highest value between selected instances to be used within an Expression?
@bybyblue pretty sure it's not intended to be used like that...
Reason being that when you pick the object with the minimum value, it will pick a single object, if there's more than one with the same value, it will pick the one that was created first (or last, something like that)
The reason the second approach works is because that won't be picking one of the objects with the minimum value, it will count all objects that have the same value, in this case, the minimum value.
I'm aware of why the second method in my example file works. Just wasn't sure if Pick Object with minimum/maximum value was intended to function the way that it currently does. As it stands I find it's use to be funky. Makes things feel somewhat random coding wise.
Well, I guess it would be "Pick Objects with minimum/maximum value" or "Pick All Objects with minimum/maximum value" if it was for multiple objects, just like you can see on New Objects conditions.
The name of stuff is usually a good hint, if you read it all, it shouldn't be confusing nor random.
But I guess what makes you confused is that it says the name of the object instead of "object", which is kind of understandable, having the name there wasn't necessary.
As NaitorStudios mentioned, the name would need to change if this change were made. I think replacing Pick Object with minimum/maximum expression value with Object has minimum/maximum expression value would do the trick. The description would match the result, and by removing the word "pick" it would separate it from the other "pick" conditions which all choose a single object.
I can't think of a situation where a new action would accomplish something that the new condition doesn't already. But if you're talking about a new expression itself - something like minimumExpressionValue(>Object<, >Expression<) - then I think that could be useful for sure.-oh and now that I think about it is there any reason why we don't have an action to grab the lowest or highest value between selected instances to be used within an Expression?
ALT + CTRL + Fill on a counter's frame will color every other frames of every counter except the one you used to fill all the frames of the counter.
Mince, c'est tellement pas clair en anglais...
En fait si je fais le ALT+CTRL+Fill sur une frame d'un compteur (ex. le 0), toutes les frames des autres compteurs vont être coloré, sauf la frame utilisée à la base (le 0).