Forums > MIRA

MIRA Automatic Scripting Name Assignment (!?)

Feb 23 2014 | 7:42 am

This drove me Insane for hours last night.
Couldn’t figure out why objects were being given generic names (flonum, flonum[1], …).
I blamed that poor little [autopattr (@autoname 0)], who was entirely innocent.
Turns out that mira.frame, (understandably, predictably, obviously) auto-assigns Scripting Names to all objects it supports if they are not already named.
Fine, no hard feelings, MIRA…. But this is a problem when I only want to use the very specifically assigned Scripting Names in a Umenu, for routing purposes with pattrstorage, and dont want 500 ‘flonum[i]’ clogging up my ipad screen.

Any suggestions for how to circumvent this?

Jan 18 2015 | 11:37 pm

I’m also struggling with this problem.
Any solution?

Feb 01 2016 | 4:15 pm

I’ve hit this problem in a slightly different setup (no mira). My work around is to attach a [loadmess varname] to any objects I want to exclude from pattr.

Mar 03 2016 | 8:19 pm

Glad to have discovered the answer to this. Not sure I agree with the "understandably, predictably, obviously" part.


Viewing 4 posts - 1 through 4 (of 4 total)

Forums > MIRA