Ok, just a quick test so far, I can verify that 'edit object definition' and the edit button in a patch/object object seems to do the same thing now.
However, there seems to be something odd with the logic, but it can also be that I don't understand exactly how it's supposed to work.
If I make a change to the k-rate code, for instance, and click the close button on the window, I get the dialog 'Unsaved changes, do you want to apply? (Yes/No/Cancel)'. However, if I click Yes, the next time I click edit, then close,I get the same question, indicating that the changes weren't in fact applied last time. Looking at my edited code, it looks like they were in fact applied, and the generated xpatch.cpp confirms this too. I would have expected that once I've applied the changes once, I wouldn't get the question again, because that implies that the changes weren't in fact applied the first time.
What does the 'Apply' option in the File menu actually do? - in a similar vain, even if I've selected this, I get the same 'Unsaved changes...' dialog when I close the editor (which seems consistent with the rest of the behavior though).
It's not that the 'Unsaved...' dialog comes up every time I open the object editor, if I open it and don't make any changes at all it doesn't come up. So it seems that the object editor considers the object to have changed if there were any changes made since the editor was opened the first time, not since the last time the changes were applied.
Ok, got to go... sorry for being brief.