feat(docs): document note tree in relation to split view

This commit is contained in:
Elian Doran
2025-04-04 21:01:05 +03:00
parent c8f2798fc2
commit 7d40405b8c
4 changed files with 59 additions and 2 deletions

View File

@@ -1743,6 +1743,20 @@
"value": "3seOhtN8uLIY",
"isInheritable": false,
"position": 20
},
{
"type": "relation",
"name": "internalLink",
"value": "OR8WJ7Iz9K4U",
"isInheritable": false,
"position": 40
},
{
"type": "relation",
"name": "internalLink",
"value": "oPVyFC7WL2Lp",
"isInheritable": false,
"position": 50
}
],
"format": "markdown",

View File

@@ -10,4 +10,15 @@ In Trilium, is possible to work with two or more notes side-by-side.
* Only horizontal splits are possible, vertical or drag & dropping is not supported.
* When at least one split is open, press the ![](https://file+.vscode-resource.vscode-cdn.net/home/elian/UI%20Elements/3_Split%20View_image.png)![](Split%20View_3_Split%20View_im.png) button next to it to close it.
* Use the ![](Split%20View_4_Split%20View_im.png)![](https://file+.vscode-resource.vscode-cdn.net/home/elian/UI%20Elements/4_Split%20View_image.png) or the ![](Split%20View_1_Split%20View_im.png)![](https://file+.vscode-resource.vscode-cdn.net/home/elian/UI%20Elements/1_Split%20View_image.png) button to move around the splits.
* Each [tab](Tabs.md) has its own split view configuration (e.g. one tab can have two notes in a split view, whereas the others are one-note views).
* Each [tab](Tabs.md) has its own split view configuration (e.g. one tab can have two notes in a split view, whereas the others are one-note views).
* The tab will indicate only the title of the main note (the first one in the list).
## Splits and the note tree & hoisting
Clicking on the content of a split will focus that split. While focused, the [Note Tree](Note%20Tree.md) will also indicate the note that is being edited.
It is possible for each of the splits to have their own [Note Hoisting](../Navigation/Note%20Hoisting.md).
When a new split is created, it will share the same note hoisting as the previous one. An easy solution to this is to simply hoist the notes after the split is created.
This is generally quite useful for reorganizing notes from one place to the other, by hoisting the old place in the first split and hoisting the new place to the second one. This will allow easy cut and paste without the tree jumping around from switching between notes.

View File

@@ -1743,6 +1743,20 @@
"value": "3seOhtN8uLIY",
"isInheritable": false,
"position": 20
},
{
"type": "relation",
"name": "internalLink",
"value": "OR8WJ7Iz9K4U",
"isInheritable": false,
"position": 40
},
{
"type": "relation",
"name": "internalLink",
"value": "oPVyFC7WL2Lp",
"isInheritable": false,
"position": 50
}
],
"format": "html",

View File

@@ -46,8 +46,26 @@
alt="">button to move around the splits.</li>
<li>Each <a href="Tabs.html">tab</a> has its own split view configuration (e.g.
one tab can have two notes in a split view, whereas the others are one-note
views).</li>
views).
<ul>
<li>The tab will indicate only the title of the main note (the first one in
the list).</li>
</ul>
</li>
</ul>
<h2>Splits and the note tree &amp; hoisting</h2>
<p>Clicking on the content of a split will focus that split. While focused,
the&nbsp;<a class="reference-link" href="Note%20Tree.html">Note Tree</a>&nbsp;will
also indicate the note that is being edited.</p>
<p>It is possible for each of the splits to have their own&nbsp;<a class="reference-link"
href="../Navigation/Note%20Hoisting.html">Note Hoisting</a>.</p>
<p>When a new split is created, it will share the same note hoisting as the
previous one. An easy solution to this is to simply hoist the notes after
the split is created.</p>
<p>This is generally quite useful for reorganizing notes from one place to
the other, by hoisting the old place in the first split and hoisting the
new place to the second one. This will allow easy cut and paste without
the tree jumping around from switching between notes.</p>
</div>
</div>
</body>