Don't open an image immediately in the edit mode

[MatejBransky]

Hi, thanks for your extension but I don't know how to use it for simple browsing because I don't want to edit an image immediately. I would like to do it maybe later but before that I need to browse which I want to edit and with immediately enabled edit mode a lot of panels are there which hides huge parts of the image so it's easier for me to open this image in a file explorer, to see it there and then maybe go back to VS Code to edit it and that's just annoying.

Or is it possible to use it with some other extension which just shows images and then open it in this extension?

Thank you for your response.

[Tyriar]

It sounds like you're the type of user that would want to keep the default image preview extension as the default and then reopen the image with. VS Code may at some point allow an edit button to be added to the image preview (microsoft/vscode#116120), but for now the way to do this would be to clear out luna.editor from your workbench.editorAssociations setting, opening an image should then show this:

Select configure and then Image Preview:

Images should now open in the image preview and to "upgrade" to Luna Paint you would need to run the View: Reopen Editor With command. If this is a common thing you could also create a custom keybinding for workbench.action.reopenWithEditor like this:

{
  "key": "ctrl+k b",
  "command": "workbench.action.reopenWithEditor"
}

[MatejBransky]

That's a clever solution! Thank you. 🙂

[Tyriar]

Will reopen to track adding this to https://github.com/lunapaint/vscode-luna-paint/wiki/Customization as it's not very obvious 🙂

[Tyriar]

Added https://github.com/lunapaint/vscode-luna-paint/wiki/Customization

[enricodias]

The popup asking to keep Luna as the default will show only once. After that, even if you didn't pick any option Luna will keep being the default even without any workbench.editorAssociations setting present.

Restarting vscode or reinstalling the extension didn't work.

[Tyriar]

@enricodias if that's so it's a bug in VS Code, could you report to https://github.com/microsoft/vscode/issues?