From a7108c0c72130d65cabc27e40089a311c9b8973d Mon Sep 17 00:00:00 2001 From: Karol Lewandowski Date: Mon, 14 Mar 2022 09:44:55 +0100 Subject: [PATCH] using_file_templates.md: resize image closer to the actual size --- .../tutorials/file_and_code_templates/using_file_templates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/topics/tutorials/file_and_code_templates/using_file_templates.md b/topics/tutorials/file_and_code_templates/using_file_templates.md index a164861e4..1092bfce8 100644 --- a/topics/tutorials/file_and_code_templates/using_file_templates.md +++ b/topics/tutorials/file_and_code_templates/using_file_templates.md @@ -85,7 +85,7 @@ Consider a language that defines multiple types of core entities, e.g., in the J Having all of those items in the File | New action group may overwhelm users with the number of options to choose. It is more user-friendly to provide a single File | New | Java Class action and let users choose a specific entity type in the creation dialog: -![Create Java class](new_java_class_popup.png){width="460" border-effect="line"} +![Create Java class](new_java_class_popup.png){width="296" border-effect="line"} This can be achieved by placing templates in the [Internal](providing_file_templates.md#internal) category, so they are not picked up by the default mechanism, and then registering a custom [`CreateFileFromTemplateAction`](upsource:///platform/lang-impl/src/com/intellij/ide/actions/CreateFileFromTemplateAction.java)