Application Building Problem

Dec 8, 2008 at 12:52am

Application Building Problem

Every time I try to build an application out of my patch, it does the build twice for some reason, so that when i open the application, there are two of the same main windows, and then everything happens twice. If I open a sub patch, there will be two of them. I didn’t have this problem on an earlier version, and I can’t figure out why it’s doing this now. any ideas??? please help!!! Thanks.

#41232
Dec 9, 2008 at 5:48am

hmm, weird bug…

is it Max5?
do you use Windows or Mac?

do you put any script when you build application?

If you use Windows, do you see two .mxf files with .exe file?
(if you use mac, can you look inside app folder to see this?)

#146620
Dec 9, 2008 at 5:43pm

i’m using max5 on a mac. when i look at the file, it only shows the one “.app”
any ideas? thanks for your help.

#146621
Dec 10, 2008 at 10:18am

#146622
Dec 10, 2008 at 7:11pm

ok. when i look in the contents, it just shows one of each file and folder. no duplicates. i was hoping that was it.

#146623
Dec 11, 2008 at 3:37pm

well, this is very interesting bug that may be worth reporting.

let me ask a few more questions:
does it happen everytime with every patch you make?
or one particular patch?
does it happen with the collective + runtime?
are you sure that you don’t do any scripting when you make app?
(i don’t know how it goes in max5 but something like include this and that)
does that happens the same if you open another collective from the app you built?
(i.e. launch the app, then go to file>open and open another collective)

#146624
Dec 11, 2008 at 6:22pm

hi. it doesn’t happen every time i build an application. i had an older version that had no problems. i haven’t tried building a collective with this patch, but i can do that and get back to you.
maybe i should explain how this started:
i had an older application that was running slowly, so i wanted to make it leaner and more efficient. I had a main patcher, and maybe 6 sub-patches. i ended up getting rid of the main patch and then turning one of the sub-patchers into the top-level patcher. i’ve looked for something that might have copied twice, or something that shows up twice in the list of patchers and externals, but there is nothing like that. would it help if i posted the patch and/or the application???
thanks for your help in this, by the way.

#146625
Dec 11, 2008 at 9:03pm

I forgot to mention that there is a little bit of scripting involved, but only very minimally. I’m using “show” and “hide” commands for objects with a [thispatcher] object in one of the subpatches. i don’t see how this could have an effect like the one i’m dealing with.

#146626
Dec 12, 2008 at 9:32am

yes it would help to see your patch, if you don’t mind.

also, at this point, since the problem doesn’t seem to be max5,
i might consider making the patch from the scratch again.
i don’t know how complicated and time-consuming your patch is,
but that might solve the problem all at once…

what i meant by scripting is extra options when you build apps,
so scripts to [thispatcher] shouldn’t have an effect.

#146627
Dec 12, 2008 at 9:35am

That type of scripting shouldn’t do anything bad to the signal.

What’s your max window saying about errors in the patch?

jrp

#146628
Dec 12, 2008 at 9:38am

One more thing i can think of is: Are you using a poly or bpatchers in there?

Because when a poly~ patch or bpatchers deal with unclosed windows in subpatchers, then those pop up as many times as the number of poly~ instances or the number of bpatchers, when you reopen the main patch.

jrp

#146629
Dec 12, 2008 at 7:00pm

i’ve attached my patch. i couldn’t find any instance of bpatchers or poly~s. the error messages i get are “extra messages for r object.”

#146630
Dec 12, 2008 at 7:29pm

Ah! That error message means, that one or more of your receive objects have a name, which contains a space momentarily.
“r all the signal” is not allowed, it must be “r allthesignal” or something along those lines.

jrp

#146631

You must be logged in to reply to this topic.