NOT a problem, but....

[cleamon]

This is not a real problem, but I'm hoping someone can explain why some of my projects behave this way:
I open the project and without making any changes, DP thinks it needs saving when I close it. I literally have not "touched" anything, not even resized the window(s).
open project, wait for it to load, click the close button -- that's it. DP prompts me to "save, don't save, or cancel".
Just curious.

[MIDI Life Crisis]

It has always been thus. It's a mystery to me.

[stubbsonic]

For me, sometimes it does, and sometimes it doesn't. I wondered if there might be some background process that it didn't finish on the last save. And every time you open the file, it finishes the background process thus changing from saved version. But that logic doesn't necessarily follow. Perhaps there is a particular VI or plugin that will always require a save.

[mikehalloran]

It has always been thus. It's a mystery to me.

Agreed. I've never worried about it.

[cleamon]

It has always been thus. It's a mystery to me.

Agreed. I've never worried about it.

Agreed. I'm not worried, just curious.

[bayswater]

Pure speculation, but maybe it's just too difficult to figure out whether a change has been made. Prompting a save on quit is an easy way to cover all the angles. Other apps (e.g. TurboCad) always prompt for a save on quit, even if you've just done one. I've also noticed that not all operations create an undo history entry, so even if you do save, perhaps not every change is kept.

[monkey man]

So very logical, Stoiv.

I concur.

[yamguitar]

I have noticed that the act of opening a project usually gets listed in the undo history; maybe it has to do with that.

[MIDI Life Crisis]

I have noticed that the act of opening a project usually gets listed in the undo history; maybe it has to do with that.

Indeed!!!

[cleamon]

I have noticed that the act of opening a project usually gets listed in the undo history; maybe it has to do with that.

But not ALL projects. That is, yes the OPEN event appears in the history, but the project does not necessarily appear "changed".
I come to the conclusion that when DP loads a project and sends the current settings to the plugins, the plugins are reporting a change back to DP, so DP marks the project as "changed". Duh.
This behavior NEVER happens with a project having NO plugins (a rare occurrence).

[mikehalloran]

I have noticed that the act of opening a project usually gets listed in the undo history; maybe it has to do with that.

But not ALL projects. That is, yes the OPEN event appears in the history, but the project does not necessarily appear "changed".
I come to the conclusion that when DP loads a project and sends the current settings to the plugins, the plugins are reporting a change back to DP, so DP marks the project as "changed". Duh.
This behavior NEVER happens with a project having NO plugins (a rare occurrence).

[billf]

This behavior NEVER happens with a project having NO plugins (a rare occurrence).

That is interesting. It suggests the possibility is that a version change to one or more of the plugins has occurred between file openings, and perhaps DP is interpreting that as a file change of some sort.

[bayswater]

It is interesting, but shouldn't be, and becomes moot if you have the habit of pressing Cmd-S, Cmd-Q when ending a session.

[tommymandel]

It is interesting, but shouldn't be, and becomes moot if you have the habit of pressing Cmd-S, Cmd-Q when ending a session.

To me, it seems like a recent development; Now it always asks to save, whereas before (I would guess) 9.01 (but maybe) 9.0, it often asked. The plug-in scenarios, coupled with DP's handling of that, would explain it.

There are times when I don't wish to save upon closing a project: I have my 'what have I done?' moments where it was delivered already and I was just messing around; times where I think it wiser to save as a name-altered iteration.

[mikehalloran]

It is interesting, but shouldn't be, and becomes moot if you have the habit of pressing Cmd-S, Cmd-Q when ending a session.

To me, it seems like a recent development; Now it always asks to save, whereas before (I would guess) 9.01 (but maybe) 9.0, it often asked. The plug-in scenarios, coupled with DP's handling of that, would explain it.

There are times when I don't wish to save upon closing a project: I have my 'what have I done?' moments where it was delivered already and I was just messing around; times where I think it wiser to save as a name-altered iteration.

Recent development... Really? When I read the first post, my only thought was "DP's always done that. So what?"

It does with DP 7.24 and 8.07 on my iMac. I checked DP 5.13, 6.03, 7.01 and 7.12 on my G4. I opened and closed various projects, nothing else. One was a straight live recording with no plugs — didn't ask to save.

I think the OP figured it out. No reason to think anything else unless somene from MOTU enlightens us further. Great. We learned something. It's not important nor has it ever affected DP performance nor caused a problem — as was admitted in the OP.

What's next?