You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/refguide/modeling/menus/edit-menu/_index.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ weight: 10
7
7
8
8
## Introduction
9
9
10
-
Via the **Edit** menu you can perform various actions, such cut/copy/paste or search where a particular document is used. You can also open the [Preferences](/refguide/preferences-dialog/) dialog that contains user-specific settings.
10
+
You can use the **Edit** menu to perform various actions, such as cut, copy, and paste, or search where a particular document is used. You can also open the [Preferences](/refguide/preferences-dialog/) dialog box that contains user-specific settings.
|**Undo** (<kbd>Ctrl</kbd> + <kbd>Z</kbd>) | Undoes the last action in a document tab. Undo and redo actions are unlimited. |
21
21
|**Redo** (<kbd>Ctrl</kbd> + <kbd>Y</kbd>) | Redoes the last action that was undone in a document tab. |
22
-
|**Cut** (<kbd>Ctrl</kbd> + <kbd>X</kbd>) | Copies the selected element to the clipboard and delete it. |
22
+
|**Cut** (<kbd>Ctrl</kbd> + <kbd>X</kbd>) | Copies the selected element to the clipboard and deletes it. |
23
23
|**Copy** (<kbd>Ctrl</kbd> + <kbd>C</kbd>) | Copies the selected element to the clipboard. |
24
24
|**Paste** (<kbd>Ctrl</kbd> + <kbd>V</kbd>) | Pastes the contents of the clipboard in the current editor. |
25
25
|**Delete** (<kbd>Delete</kbd>) | Deletes the selected element. |
26
-
|**Find** (<kbd>Ctrl</kbd> + <kbd>F</kbd>) | Searches the model for text. The following texts are searched: all texts that appear in the end-user interface (for example captions of labels or buttons); names and documentation of documents; entity, association, and attribute names and documentation; access rule documentation; page widget names; captions and documentation of microflow objects; and names of items in microflows. |
26
+
|**Find** (<kbd>Ctrl</kbd> + <kbd>F</kbd>) | Searches the model for text. The following texts are searched: all texts that appear in the end-user interface (for example, captions of labels or buttons); names and documentation of documents; entity, association, and attribute names and documentation; access rule documentation; page widget names; captions and documentation of microflow objects; and names of items in microflows. |
27
27
|**Find Advanced** (<kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>F</kbd>) | Opens a dialog box that allows for advanced search operations. Examples are searching for any document type and searching for unused documents. |
28
28
|**Find Usages** (<kbd>Ctrl</kbd> + <kbd>Alt</kbd> + <kbd>F</kbd>) | Opens the **Find Results** pane and displays usages of the selected object. |
29
29
|**Go to** (<kbd>Ctrl</kbd> + <kbd>G</kbd>) | Quickly navigates to any document or domain model element in the app by typing a few letters and pressing <kbd>Enter</kbd>. |
30
-
|**Next Find Result** (<kbd>F3</kbd>) | Highlights the next find result in the **Find Results** pane and open it in an editor. |
31
-
|**Previous Find Result** (<kbd>Shift</kbd> + <kbd>F3</kbd>) | Highlights the previous find result in the **Find Results** pane and open it in an editor. |
32
-
|**Back** (<kbd>Ctrl</kbd> + <kbd>-</kbd>) |Move backward through your editing history to show the documents you have recently worked on. |
33
-
|**Forward** (<kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>-</kbd>) |Move forward through your editing history to show the documents you have recently worked on. |
34
-
|**Next Error** (<kbd>F8</kbd>) | Highlights the next error in the **Error List** pane and open it in an editor. |
35
-
|**Previous Error** (<kbd>Shift</kbd> + <kbd>F8</kbd>) | Highlights the previous error result in the **Error List** pane and open it in an editor. |
30
+
|**Next Find Result** (<kbd>F3</kbd>) | Highlights the next find result in the **Find Results** pane and opens it in an editor. |
31
+
|**Previous Find Result** (<kbd>Shift</kbd> + <kbd>F3</kbd>) | Highlights the previous find result in the **Find Results** pane and opens it in an editor. |
32
+
|**Back** (<kbd>Ctrl</kbd> + <kbd>-</kbd>) |Moves backward through your editing history to show the documents you have recently worked on. |
33
+
|**Forward** (<kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>-</kbd>) |Moves forward through your editing history to show the documents you have recently worked on. |
34
+
|**Next Error** (<kbd>F8</kbd>) | Highlights the next error in the **Error List** pane and opens it in an editor. |
35
+
|**Previous Error** (<kbd>Shift</kbd> + <kbd>F8</kbd>) | Highlights the previous error result in the **Error List** pane and opens it in an editor. |
36
36
|**Preferences**| Opens the **Preferences** dialog box, where you can set your general, model, and advanced editing preferences. For more information on the **Preferences** dialog box, see [Preferences](/refguide/preferences-dialog/). |
Copy file name to clipboardExpand all lines: content/en/docs/refguide/modeling/menus/edit-menu/find-and-find-advanced.md
+24-20Lines changed: 24 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,16 +7,16 @@ weight: 10
7
7
8
8
## Introduction
9
9
10
-
You can search for changes or usages of different elements, documents, XPaths, changes to various elements, in your app. You do it via**Find**, **Find Advanced**, and **Find Usages** options under the **Edit** menu.
10
+
You can search for changes or usages of different elements, documents, and XPathsin your app. You can do this with the**Find**, **Find Advanced**, and **Find Usages** options under the **Edit** menu.
You can find various elements in your app via the **Find** option. For example, you would like to find elements in the domain model, page editor, and microflow editor where the word "Employee" is used: pages, entities, associations, expressions with it, etc. Do the following:
16
+
You can find various elements in your app with the **Find** option. For example, to find elements in the domain model, page editor, and microflow editor where the word "Employee" is used (such as pages, entities, associations, and expressions), do the following:
17
17
18
-
1. Click **Edit** > **Find** in the top-bar or press <kbd>Ctrl</kbd> + <kbd>F</kbd>.
19
-
2. In the **Find** dialog box, leave **Match case** and **Match the whole word** unselected. This way you will search for all instances of the word "Employee" including such instances as "employee", Employees", or "Department_Employee":
18
+
1. Click **Edit** > **Find** in the topbar or press <kbd>Ctrl</kbd> + <kbd>F</kbd>.
19
+
2. In the **Find** dialog box, leave **Match case** and **Match the whole word** unselected. This way you will search for all instances of the word "Employee" including such instances as "employee", "Employees", or "Department_Employee":
@@ -26,14 +26,14 @@ You can see search results in the **Find Results** pane:
26
26
27
27
## Find Advanced Option {#find-advanced}
28
28
29
-
With the **Find Advanced** option you can set advanced criteria and find specific elements in your app, such as all [object activities](#find-object-activities), or [unused elements](#find-unused-elements).
29
+
With the **Find Advanced** option, you can set advanced criteria and find specific elements in your app, such as all [object activities](#find-object-activities) or [unused elements](#find-unused-elements).
@@ -43,7 +43,7 @@ You can see search results in the **Find Results** pane.
43
43
44
44
### Finding Unused Elements {#find-unused-elements}
45
45
46
-
While you develop your app, it might occur that specific functionality (for example, pages or microflows) is not applicable anymore in the final version of your application. To keep your app clear and easy to maintain, it is advised to clean any unused items up.
46
+
While you develop your app, specific functionality (for example, pages or microflows) might not be applicable anymore in the final version of your application. To keep your app clear and easy to maintain, clean up any unused items.
47
47
48
48
To find the unused items, do the following:
49
49
@@ -54,9 +54,9 @@ To find the unused items, do the following:
54
54
55
55
3. Click **Find**.
56
56
57
-
The results will show up in the **Find Results** pane. To filter the results click the **Show all** button in the upper-right corner of the pane.
57
+
The results show up in the **Find Results** pane. To filter the results, click the **Show all** button in the upper-right corner of the pane.
58
58
59
-
Note that deleting any unused items might result in more unused items. For example, if you delete an unused page, a microflow which is only used on that page will become an unused item itself. If you are cleaning up your app regularly refresh the unused items list.
59
+
Deleting any unused items might result in more unused items. For example, if you delete an unused page, a microflow that is only used on that page will become an unused item itself. If you are cleaning up your app, regularly refresh the unused items list.
60
60
61
61
{{% alert color="info" %}}
62
62
Modules downloaded from the Marketplace might contain a lot of unused items. If you remove those items and the module is updated later, those items will be back in your model, so it is advised that you do not remove any unused items from an Marketplace module.'
@@ -68,31 +68,35 @@ Any objects which are excluded from the app will not show up in the unused items
68
68
69
69
### Marking Unused Objects as Used
70
70
71
-
Some pages and microflows are only used from Java code and will be listed as an unused item because Studio Pro cannot look into Java source code. To prevent anyone from removing these objects you can mark the page or microflow as used. Do the following:
71
+
Some pages and microflows are only used from Java code and will be listed as an unused item because Studio Pro cannot look into Java source code. To prevent anyone from removing these objects, you can mark the page or microflow as used. Do the following:
72
72
73
-
1. Open the page or microflow which needs to be marked as used.
74
-
2. Open the **Edit** menu and select **Properties**, then change the **Mark as used** property from **No** to **Yes**.
73
+
1. Open the page or microflow that needs to be marked as used.
74
+
2. Open the **Edit** menu and select **Properties**.
75
+
3. Change the **Mark as used** property from **No** to **Yes**.
75
76
76
77
## Find Usages Option {#find-usages}
77
78
78
-
The **Find Usages** option allows you to find where a certain element is used, for example, to find all buttons that open a certain page.
79
+
The **Find Usages** option finds where a certain element is used, for example, all buttons that open a certain page.
79
80
80
81
{{% alert color="info" %}}
81
-
This option only finds places where the selected entity/attribute is selected itself. This means that it will not find instances where the entity/attribute is derived implicitly (for example, by following an association).
82
+
This option only finds places where the selected entity or attribute is directly selected. It does not find instances where the entity or attribute is derived implicitly, such as by following an association.
82
83
{{% /alert %}}
83
84
84
85
To find where a certain element is used, do the following:
85
86
86
-
1. Open the document which contains the element. For example, open the domain model.
87
-
2. Select an element (for example, an entity) and click **Edit** > **Find usages** in the top-bar or right-click an element and select **Find usages**:
87
+
1. Open the document that contains the element, such as the domain model.
88
+
2. Select an element, such as an entity.
89
+
3. Click **Edit** > **Find usages** in the top bar, or right-click the element.
Double-click an item in the **Find Results** pane to open the corresponding document.
97
+
Double-click an item in the **Find Results** pane to open the corresponding document.
94
98
95
-
Click **Lock results** in the **Find Results** pane. Now if you click **Find Usages**, the results will be shown in a second **Find Results** pane. This allows you to keep several search results.
99
+
Click **Lock results** in the **Find Results** pane to keep the current results. The next time you click **Find Usages**, the results display in a second **Find Results** pane. This allows you to keep several search results.
Copy file name to clipboardExpand all lines: content/en/docs/refguide/modeling/menus/edit-menu/go-to-option.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,33 +7,33 @@ weight: 40
7
7
8
8
## Introduction
9
9
10
-
In Studio Pro editors, such as navigation, page, or microflow editor, you can access a handy menu by right-clicking items. A**Go to** option is commonly used to find your way in an app. It allows you to navigate from one element to another: for example, to navigate to the target of a button or to the source of a data grid.
10
+
In Studio Pro editors, such as the navigation, page, or microflow editor, you can access a handy menu by right-clicking items. The**Go to** option is commonly used to find your way in an app. It allows you to navigate from one element to another, for example, to navigate to the target of a button or to the source of a data grid.
11
11
12
12
## The Go to Option
13
13
14
14
The examples of using the **Go to** option are described below:
15
15
16
-
***Opening a target of a menu item** – in **App** > **Navigation**, you can right-click a menu item and select **Go to target**. Studio Pro will open the corresponding target of the menu item,for example, a page.
16
+
***Opening a target of a menu item** – in **App** > **Navigation**, you can right-click a menu item and select **Go to target**. Studio Pro opens the corresponding target of the menu item,for example, a page.
17
17
18
18
{{< figure src="/attachments/refguide/modeling/menus/edit-menu/go-to-option/go-to-target.png" alt="Go to Target" class="no-border" width="600" >}}
19
19
20
-
***Opening a data source of an element** – on pages, you can navigate to the data source of a widget. For example, you can right-click a button in the data grid and select **Go to microflow**. Mendix Studio Pro will open the corresponding microflow:
20
+
***Opening a data source of an element** – on pages, you can navigate to the data source of a widget. For example, you can right-click a button in the data grid and select **Go to microflow**. Mendix Studio Pro opens the corresponding microflow:
21
21
22
22
{{< figure src="/attachments/refguide/modeling/menus/edit-menu/go-to-option/go-to-microflow.png" alt="Go to Microflow" class="no-border" width="500" >}}
23
23
24
-
***Opening an entity from a microflow** – you can navigate to an entity in the domain model if you right-click an activity in the microflow and select **Go to entity**. Mendix Studio Pro will open the corresponding domain model:
24
+
***Opening an entity from a microflow** – you can navigate to an entity in the domain model if you right-click an activity in the microflow and select **Go to entity**. Mendix Studio Pro opens the corresponding domain model:
25
25
26
26
{{< figure src="/attachments/refguide/modeling/menus/edit-menu/go-to-option/go-to-entity.png" alt="Go to Entity" class="no-border" width="400" >}}
27
27
28
28
## The Go to Dialog {#go-to-dialog}
29
29
30
-
The **Go to** dialog can be accessed by both the **Edit** menu or by using the <kbd>Ctrl</kbd> + <kbd>G</kbd> shortcut. The dialog allows quick navigation to any document or domain model element in the app by typing a few letters and pressing <kbd>Enter</kbd>.
30
+
The **Go to** dialog box can be accessed by both the **Edit** menu or by using the <kbd>Ctrl</kbd> + <kbd>G</kbd> shortcut. The dialog box allows quick navigation to any document or domain model element in the app by typing a few letters and pressing <kbd>Enter</kbd>.
31
31
32
32
{{< figure src="/attachments/refguide/modeling/menus/edit-menu/go-to-option/go-to-dialog.png" alt="Go to Dialog" width="400" >}}
33
33
34
-
The typed letters or term are cached, so if the dialog is closed and reopened, the input is not lost.
34
+
The typed letters or term are cached, so if the dialog box is closed and reopened, the input is not lost.
35
35
36
-
This dialog also supports a filter option. The filter selection is saved upon both closing and reopening the dialog, and over different user sessions. This means the filter selection is saved even if you close and reopen Studio Pro.
36
+
This dialog box also supports a filter option. The filter selection is saved when you close and reopen the dialog box, and it persists over different user sessions. This means the filter selection is saved even if you close and reopen Studio Pro.
0 commit comments