From 3503582f6d4f4b4da5897b71a9c6b94b6aca8401 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yann=20C=C3=A9bron?= Date: Thu, 22 Jul 2021 12:41:50 +0200 Subject: [PATCH] dialog_wrapper.md: link "Layout" topic --- topics/user_interface_components/dialog_wrapper.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/topics/user_interface_components/dialog_wrapper.md b/topics/user_interface_components/dialog_wrapper.md index fcd38a18f..5bdc0b87a 100644 --- a/topics/user_interface_components/dialog_wrapper.md +++ b/topics/user_interface_components/dialog_wrapper.md @@ -37,7 +37,9 @@ The `DialogWrapper` class is often used together with [GUI Designer forms](https In this case, bind a GUI Designer form to the class extending `DialogWrapper`, bind the top-level panel of the form to a field and return that field from the `createCenterPanel()` method. When using Kotlin, use [Kotlin UI DSL](kotlin_ui_dsl.md) to provide the dialog's contents. - > Existing dialogs can be inspected at runtime using [UI Inspector](internal_ui_inspector.md), e.g., to locate the underlying implementation of UI components. + > See [Layout](https://jetbrains.design/intellij/principles/layout) topic in IntelliJ Platform UI Guidelines for recommendations on arranging UI controls in dialogs. + > + > Existing dialogs can be inspected at runtime using [UI Inspector](internal_ui_inspector.md), e.g., to locate the underlying implementation of UI components. > {type="tip"}