autopattr and mira incompatibility


    Dec 29 2014 | 6:58 pm
    Hello there,
    I come to a problem recently using pattrstorage and autopattr in my patcher at the same time. Actually it seems that the presence of a mira.frame in your patcher make all ui object in this patcher to be named with parameter mode enable. So they are automatically added to the pattr system due to autopattr.
    So instead of save & restore the GUI object I named myself it does it for every GUI objects in my patcher and subpatcher. And I don't want that at all.
    I tried to inactivate some of those gui in the clientwindow but it doesn't work. The only solution seems to link the object manually via the pattr object, ok for a few one but for larger numbers it became complicated.
    Did some of you had the same issue ?

    • Jan 19 2015 | 7:43 am
      I have exactly same issue, wandering why only one or two people have mentioned on it in this forum. I want officials to comment on this problem, at least...
    • Jan 19 2015 | 9:27 pm
      They told me that they had written a ticket for the programming team three weeks ago, no news since...
    • Apr 09 2015 | 9:08 am
      Any news on this problem ? Has someone test it with the new Mira package 1.1.8 ?
    • Apr 09 2015 | 9:08 pm
      did you try unchecking objects in pattrstorage storagewindow? it works for me or connect the UI you don't want to save to the second outlet of autopattr?
    • Apr 10 2015 | 3:56 pm
      This issue still exists. I recently had an exchange with C74 support about this. Here was the reply:
      In order to do it's thing, mira.frame also needs to give scripting names to UI objects on the same patcher level. So, a workaround is to put the mira.frame object and any of the relevant UI objects in a subpatcher.
      I can confirm that this works, and the solution that Florent Ghys suggests will also work.