At launch, prevent a document-based app to reopen an unsaved-unedited-empty document that was opened when...
In a simple rtf editor —based on NSDocument subclass—, when app starts, it creates an untitled file. This a desirable behaviour. But if I quit the app with this opened, unedited and unsaved document (empty!), the application will restore this document at the next launch.
How can I set this document so that it cannot be restored. If I uncheck the window's controller window "Restorable" property in IB, no document is restored ever, which is not the desirable behaviour: edited-saved documents that were not closed by user need being restored; untitled-unedited documents should not!
macos nsapplication-delegate
asked Nov 20 '18 at 0:06
DenisDenis
401418
add a comment |
In a simple rtf editor —based on NSDocument subclass—, when app starts, it creates an untitled file. This a desirable behaviour. But if I quit the app with this opened, unedited and unsaved document (empty!), the application will restore this document at the next launch.
How can I set this document so that it cannot be restored. If I uncheck the window's controller window "Restorable" property in IB, no document is restored ever, which is not the desirable behaviour: edited-saved documents that were not closed by user need being restored; untitled-unedited documents should not!
macos nsapplication-delegate
asked Nov 20 '18 at 0:06
DenisDenis
401418
Do you mean it's ending up with two untitled documents, the one from launching the app and the other being restored? Or is there only one? If there's only one, what's the difference between it being new or being restored?
– Ken Thomases
Nov 20 '18 at 1:04
No. When there is only one document opened (the empty untitled one) as I quit, it is restored but no new untitled is created. But if I have one edited/saved document and the empty one as I quit, both are restored… What is strange is that the initial position window is always ignored, any new or restored window cascade from the middle of the screen…
– Denis
Nov 20 '18 at 11:09
add a comment |
In a simple rtf editor —based on NSDocument subclass—, when app starts, it creates an untitled file. This a desirable behaviour. But if I quit the app with this opened, unedited and unsaved document (empty!), the application will restore this document at the next launch.
How can I set this document so that it cannot be restored. If I uncheck the window's controller window "Restorable" property in IB, no document is restored ever, which is not the desirable behaviour: edited-saved documents that were not closed by user need being restored; untitled-unedited documents should not!
macos nsapplication-delegate
asked Nov 20 '18 at 0:06
DenisDenis
401418
In a simple rtf editor —based on NSDocument subclass—, when app starts, it creates an untitled file. This a desirable behaviour. But if I quit the app with this opened, unedited and unsaved document (empty!), the application will restore this document at the next launch.
How can I set this document so that it cannot be restored. If I uncheck the window's controller window "Restorable" property in IB, no document is restored ever, which is not the desirable behaviour: edited-saved documents that were not closed by user need being restored; untitled-unedited documents should not!
macos nsapplication-delegate
macos nsapplication-delegate
asked Nov 20 '18 at 0:06
DenisDenis
401418
asked Nov 20 '18 at 0:06
DenisDenis
401418
asked Nov 20 '18 at 0:06
DenisDenis
401418
asked Nov 20 '18 at 0:06
DenisDenis
401418
asked Nov 20 '18 at 0:06
DenisDenis
401418
401418
Do you mean it's ending up with two untitled documents, the one from launching the app and the other being restored? Or is there only one? If there's only one, what's the difference between it being new or being restored?
– Ken Thomases
Nov 20 '18 at 1:04
No. When there is only one document opened (the empty untitled one) as I quit, it is restored but no new untitled is created. But if I have one edited/saved document and the empty one as I quit, both are restored… What is strange is that the initial position window is always ignored, any new or restored window cascade from the middle of the screen…
– Denis
Nov 20 '18 at 11:09
add a comment |
Do you mean it's ending up with two untitled documents, the one from launching the app and the other being restored? Or is there only one? If there's only one, what's the difference between it being new or being restored?
– Ken Thomases
Nov 20 '18 at 1:04
No. When there is only one document opened (the empty untitled one) as I quit, it is restored but no new untitled is created. But if I have one edited/saved document and the empty one as I quit, both are restored… What is strange is that the initial position window is always ignored, any new or restored window cascade from the middle of the screen…
– Denis
Nov 20 '18 at 11:09
Do you mean it's ending up with two untitled documents, the one from launching the app and the other being restored? Or is there only one? If there's only one, what's the difference between it being new or being restored?
– Ken Thomases
Nov 20 '18 at 1:04
Do you mean it's ending up with two untitled documents, the one from launching the app and the other being restored? Or is there only one? If there's only one, what's the difference between it being new or being restored?
– Ken Thomases
Nov 20 '18 at 1:04
No. When there is only one document opened (the empty untitled one) as I quit, it is restored but no new untitled is created. But if I have one edited/saved document and the empty one as I quit, both are restored… What is strange is that the initial position window is always ignored, any new or restored window cascade from the middle of the screen…
– Denis
Nov 20 '18 at 11:09
No. When there is only one document opened (the empty untitled one) as I quit, it is restored but no new untitled is created. But if I have one edited/saved document and the empty one as I quit, both are restored… What is strange is that the initial position window is always ignored, any new or restored window cascade from the middle of the screen…
– Denis
Nov 20 '18 at 11:09
add a comment |
1 Answer
1
active
oldest
votes
I found a solution. First, I subclassed NSDocumentController and added in its implementation file:
+ (void)restoreWindowWithIdentifier:(NSString *)identifier state:(NSCoder *)state completionHandler:(void (^)(NSWindow *, NSError *))completionHandler
{
NSInteger restorable = [state decodeIntegerForKey:@"restorable"];
if (!restorable) {
completionHandler(nil, [NSError errorWithDomain:NSCocoaErrorDomain code:NSUserCancelledError userInfo:nil]);
}
else {
[super restoreWindowWithIdentifier:identifier state:state completionHandler:completionHandler];
}
}
Then I added code in my NSDocument subclass implementation file
- (void) encodeRestorableStateWithCoder:(NSCoder *) coder {
if (self.fileURL){
[coder encodeInteger:1 forKey:@"restorable"];
} else {
[coder encodeInteger:0 forKey:@"restorable"];
}
[super encodeRestorableStateWithCoder:coder];
}
So the flag is set to 0 for any untitled document with a nil fileURL and there will be no restoration a launch. Other documents are restored.
answered Nov 28 '18 at 19:56
DenisDenis
401418
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53384395%2fat-launch-prevent-a-document-based-app-to-reopen-an-unsaved-unedited-empty-docu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I found a solution. First, I subclassed NSDocumentController and added in its implementation file:
+ (void)restoreWindowWithIdentifier:(NSString *)identifier state:(NSCoder *)state completionHandler:(void (^)(NSWindow *, NSError *))completionHandler
{
NSInteger restorable = [state decodeIntegerForKey:@"restorable"];
if (!restorable) {
completionHandler(nil, [NSError errorWithDomain:NSCocoaErrorDomain code:NSUserCancelledError userInfo:nil]);
}
else {
[super restoreWindowWithIdentifier:identifier state:state completionHandler:completionHandler];
}
}
Then I added code in my NSDocument subclass implementation file
- (void) encodeRestorableStateWithCoder:(NSCoder *) coder {
if (self.fileURL){
[coder encodeInteger:1 forKey:@"restorable"];
} else {
[coder encodeInteger:0 forKey:@"restorable"];
}
[super encodeRestorableStateWithCoder:coder];
}
So the flag is set to 0 for any untitled document with a nil fileURL and there will be no restoration a launch. Other documents are restored.
answered Nov 28 '18 at 19:56
DenisDenis
401418
add a comment |
I found a solution. First, I subclassed NSDocumentController and added in its implementation file:
+ (void)restoreWindowWithIdentifier:(NSString *)identifier state:(NSCoder *)state completionHandler:(void (^)(NSWindow *, NSError *))completionHandler
{
NSInteger restorable = [state decodeIntegerForKey:@"restorable"];
if (!restorable) {
completionHandler(nil, [NSError errorWithDomain:NSCocoaErrorDomain code:NSUserCancelledError userInfo:nil]);
}
else {
[super restoreWindowWithIdentifier:identifier state:state completionHandler:completionHandler];
}
}
Then I added code in my NSDocument subclass implementation file
- (void) encodeRestorableStateWithCoder:(NSCoder *) coder {
if (self.fileURL){
[coder encodeInteger:1 forKey:@"restorable"];
} else {
[coder encodeInteger:0 forKey:@"restorable"];
}
[super encodeRestorableStateWithCoder:coder];
}
So the flag is set to 0 for any untitled document with a nil fileURL and there will be no restoration a launch. Other documents are restored.
answered Nov 28 '18 at 19:56
DenisDenis
401418
add a comment |
I found a solution. First, I subclassed NSDocumentController and added in its implementation file:
+ (void)restoreWindowWithIdentifier:(NSString *)identifier state:(NSCoder *)state completionHandler:(void (^)(NSWindow *, NSError *))completionHandler
{
NSInteger restorable = [state decodeIntegerForKey:@"restorable"];
if (!restorable) {
completionHandler(nil, [NSError errorWithDomain:NSCocoaErrorDomain code:NSUserCancelledError userInfo:nil]);
}
else {
[super restoreWindowWithIdentifier:identifier state:state completionHandler:completionHandler];
}
}
Then I added code in my NSDocument subclass implementation file
- (void) encodeRestorableStateWithCoder:(NSCoder *) coder {
if (self.fileURL){
[coder encodeInteger:1 forKey:@"restorable"];
} else {
[coder encodeInteger:0 forKey:@"restorable"];
}
[super encodeRestorableStateWithCoder:coder];
}
So the flag is set to 0 for any untitled document with a nil fileURL and there will be no restoration a launch. Other documents are restored.
answered Nov 28 '18 at 19:56
DenisDenis
401418
I found a solution. First, I subclassed NSDocumentController and added in its implementation file:
+ (void)restoreWindowWithIdentifier:(NSString *)identifier state:(NSCoder *)state completionHandler:(void (^)(NSWindow *, NSError *))completionHandler
{
NSInteger restorable = [state decodeIntegerForKey:@"restorable"];
if (!restorable) {
completionHandler(nil, [NSError errorWithDomain:NSCocoaErrorDomain code:NSUserCancelledError userInfo:nil]);
}
else {
[super restoreWindowWithIdentifier:identifier state:state completionHandler:completionHandler];
}
}
Then I added code in my NSDocument subclass implementation file
- (void) encodeRestorableStateWithCoder:(NSCoder *) coder {
if (self.fileURL){
[coder encodeInteger:1 forKey:@"restorable"];
} else {
[coder encodeInteger:0 forKey:@"restorable"];
}
[super encodeRestorableStateWithCoder:coder];
}
So the flag is set to 0 for any untitled document with a nil fileURL and there will be no restoration a launch. Other documents are restored.
answered Nov 28 '18 at 19:56
DenisDenis
401418
answered Nov 28 '18 at 19:56
DenisDenis
401418
answered Nov 28 '18 at 19:56
DenisDenis
401418
answered Nov 28 '18 at 19:56
DenisDenis
401418
401418
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53384395%2fat-launch-prevent-a-document-based-app-to-reopen-an-unsaved-unedited-empty-docu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Do you mean it's ending up with two untitled documents, the one from launching the app and the other being restored? Or is there only one? If there's only one, what's the difference between it being new or being restored?
– Ken Thomases
Nov 20 '18 at 1:04
No. When there is only one document opened (the empty untitled one) as I quit, it is restored but no new untitled is created. But if I have one edited/saved document and the empty one as I quit, both are restored… What is strange is that the initial position window is always ignored, any new or restored window cascade from the middle of the screen…
– Denis
Nov 20 '18 at 11:09