Default Application

[Tim]

Change the name of the old DP app(s), like add a letter or number to it, then see if 'change all to open with' works.

If that fails, just drag the older version(s) to a backup drive, then trash them from the system drive.
Or just trash them and don't look back.

[Freaky Freddy]

Tim,

The default app. did change when I altered the name from 7.12.
Now default app. is 7.2.

Also, bjornin, the method described earlier, with the alt. button
worked, but then it messed up once as well, I received some error
message.

Onyx method I never put through the grinder.

Thanks all for the assistance!

FF

[MIDI Life Crisis]

The usual GET INFO thing isn't working here either. There is clearly something in the file TYPE in DP 7 files that is broken. Here's the strange part...

If I tell the FINDER to OPEN ALL similar files, it won't and the file reverts to 7.12, but if I DON'T select that option and simply dismiss the GET INFO box after selecting OPEN WITH, that file then opens with 7.2 from that point on. This only happens in DP. No other app appears to be affected.

Reported to MOTU via Techlink

MOTU?

[Also posted in http://www.motunation.com/forum/viewtop ... 26&t=42631" onclick="window.open(this.href);return false; ]

[Radiogal]

Honestly, why do you open a project without starting DP first and open it from whithin DP? What´s the gain, really? Okay, a lill shortcut..
I tried it before in different versions of DP, but I only had bad experiences trying to open DP just by clicking the project icon itself.
I felt DP wasn´t so comfortable with it, and that it may result in unexpected errors and crashes.. so I never did it again.

Hmm, that makes me wonder..
Those who are tiered of the beachball-party, errors and strange DP behavoiur.. how do YOU open your projects??

[bjornln]

Honestly, why do you open a project without starting DP first and open it from whithin DP? What´s the gain, really? Okay, a lill shortcut..
I tried it before in different versions of DP, but I only had bad experiences trying to open DP just by clicking the project icon itself.
I felt DP wasn´t so comfortable with it, and that it may result in unexpected errors and crashes.. so I never did it again.

Hmm, that makes me wonder..
Those who are tiered of the beachball-party, errors and strange DP behavoiur.. how do YOU open your projects??

I usually work with just a few projects simultaneously, not more than what will fit on the "recents" sub menu. So, I goto the dock and click DP....
If I need to dig down deeper on my server, I just double click on the file.
Once in a while I "upgrade" my DP Projects to the most recent version.
Just to be sure that you still can open them.


/B

[Radiogal]

I´m not having any problems. That´s not my point. I always open the DP version first before opening a project, most often, like bjornin, from "recent projects". No problem at all.

I just wonder if those who open DP by clicking on the project icon experience more crashes/errors than those who open the DP app first. Just a thought..

[MIDI Life Crisis]

Honestly, why do you open a project without starting DP first and open it from whithin DP? What´s the gain, really?

Well it goes a little deeper than that. Sure, open the project from DP. Easy. BUT... (and it's a big butt!!)

IF - the current version of DP is not recognized as the app of record for a file,

THEN - the file may get corrupted - especially at SAVE.

THEREFORE - the file might not be recognized by the app and you get an error message, such as the dreaded -39 error some of us have experienced.

SO - it behooves MOTU to find out why this is happening and fix it as plist errors like this are potentially very serious.

[cuttime]

Copied from another thread:


I know all of you are not using Snow Leopard, but I can't help but wonder if DP is not supporting creator codes any longer, because Apple is not supporting them either.

More info:
http://arstechnica.com/staff/fatbits/20 ... adness.ars" onclick="window.open(this.href);return false;

And a $5 workaround:
http://pagehand.com/launchcodes/" onclick="window.open(this.href);return false;