<!--
{
  "availability" : [
    "iOS: 3.0.0 -",
    "iPadOS: 3.0.0 -",
    "macCatalyst: 13.1.0 -",
    "macOS: 10.0.0 -",
    "tvOS: 9.0.0 -",
    "visionOS: 1.0.0 -",
    "watchOS: 2.0.0 -"
  ],
  "documentType" : "symbol",
  "framework" : "Foundation",
  "identifier" : "/documentation/Foundation/NSNotification/Name-swift.struct/NSUndoManagerDidUndoChange",
  "metadataVersion" : "0.1.0",
  "role" : "Type Property",
  "symbol" : {
    "kind" : "Type Property",
    "modules" : [
      "Foundation"
    ],
    "preciseIdentifier" : "c:@NSUndoManagerDidUndoChangeNotification"
  },
  "title" : "NSUndoManagerDidUndoChange"
}
-->

# NSUndoManagerDidUndoChange

Posted just after an undo manager performs an undo operation.

```
static let NSUndoManagerDidUndoChange: NSNotification.Name
```

## Discussion

If you invoke [`undo()`](/documentation/Foundation/UndoManager/undo()) or [`undoNestedGroup()`](/documentation/Foundation/UndoManager/undoNestedGroup()), this notification is posted. The notification object is the [`UndoManager`](/documentation/Foundation/UndoManager) object. This notification doesn’t contain a `userInfo` dictionary.

The system posts this notification on the actor, thread, or dispatch queue that calls [`undo()`](/documentation/Foundation/UndoManager/undo()).

---

Copyright &copy; 2026 Apple Inc. All rights reserved. | [Terms of Use](https://www.apple.com/legal/internet-services/terms/site.html) | [Privacy Policy](https://www.apple.com/privacy/privacy-policy)