just upgraded from 5 to 5.0.5 (PPC). a program that worked fine with max5 (until 2 hours ago) does not do so any more with 5.0.5.

starting up the program asks to select a filefolder (opendialog fold). instead of accepting, it asks to select a folder again and again. i have to kill the prog to get out of this loop. 

what could have changed in the upgrade to have this result? 

do i have to downgrade to 5 to look at the code? 

just upgraded from 5 to 5.0.5 (PPC). a program that worked fine with max5 (until 2 hours ago) does not do so any more with 5.0.5.
starting up the program asks to select a filefolder (opendialog fold). instead of accepting, it asks to select a folder again and again. i have to kill the prog to get out of this loop. 
2 other programs work just as expected. 
what could have changed in the upgrade to have this result? 
do i have to downgrade to 5 to look at the code?  
best, uea


5-0-5-problem-opendialog-fold

> do i have to downgrade to 5 to look at the code?

It's possible to open as text and change the name of the opendialog into one that doesn't exist.

> what could have changed in the upgrade to have this result?

Automated loading sequences require some more attention then they used to, is my experience, and they might behave different on various configurations. Use a deferlow after the loadbang. I've gone through the same proces (updating older work for max 5) and found myself spending most time on this. Otherwise and a bit to my surprise I have to admit, patches would perform just fine when opened in five.

thnks for the deferlow-tip. i will try...

actually it does not do much in this process, no loading of files, just setting project folder, midi and audio setup...

yes actually it was running in 5. but not in 5.0.5

yes that is what i did in the meanwhile. 

thnks for the deferlow-tip. i will try...
actually it does not do much in this process, no loading of files, just setting project folder, midi and audio setup... 

yes actually it was running in 5. but not in 5.0.5
best, uea


Loadbanging a opendialog appears not to be problematic in itself. Apparently what happens after is what creates the trouble. Who knows you can isolate it and post it.

you were right. i dont really understand which messages or processes could have possibly interfered there. i am also surprised... 

you were right. i dont really understand which messages or processes could have possibly interfered there. i am also surprised... 
thanks johan 
julean


The opendialog problem has not been solved: it still happens in 5.0.5 and 5.0.6. Here is a part of a patch: on my machine (MacBook Pro, 10.5.4, max-msp 5.0.6) it asks for a filename twice. If I cut the cord marked in red and rerun the patch it asks only one time. With the other stuff that I have in the patch it even asks three times. This is all reproducible: I've had the situation in several patches. What's worse is if I compile a standalone it works as expected.

1, 01Jeestunautre.aif;
2, 02Jeestunautre.aif;
3, 03Jeestunautre.aif;
4, 04Jeestunautre.aif;
5, 05Jeestunautre.aif;
6, 06Jeestunautre.aif;


Did you try using deferlow as Johan suggested?


Yes I'm using that workaround:-), (thanks johan), but it doesn't change the fact that the object has a bug somewhere:-(. Maybe opendialog could just deferlow itself...

Yes I'm using that workaround:-), (thanks johan),  but it doesn't change the fact that the object has a bug somewhere:-(. Maybe opendialog could just deferlow itself...

5.0.5 problem opendialog fold