# MojoPad 1.92.0 Released (Bug Fixes) (User Requests) **URL:** \ **Category:** MojoPad\ **Created:** [September 6, 2026, 7:14pm UTC](https://mojopad.discourse.group/t/mojopad-1-92-0-released-bug-fixes-user-requests/186 "2026-09-06T19:14:19Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Mark\_Busse](https://yyz1.discourse-cdn.com/flex003/user_avatar/mojopad.discourse.group/mark_busse/32/43_2.png) [@Mark\_Busse](https://mojopad.discourse.group/u/Mark_Busse)\ **Post date:** [September 6, 2026, 7:14pm UTC](https://mojopad.discourse.group/t/mojopad-1-92-0-released-bug-fixes-user-requests/186/1 "2026-09-06T19:14:19Z")
**Reading two pages at once, and asking one thing of several sources** - **Every list of pages now opens one in a window of its own.** Right-click a row in search results, in Context, Backlinks, Related and Rediscover, in the Pages pane, or in the source picker, and choose **Open in Small Window** — or **⇄ Open Beside This Page** to put it in the split pane. Comparing two pages no longer means opening one, going back, and searching again. A window on the same wiki saves into it and says so if you have both open on the same page. - **Panes stack.** **＋ Add a Pane** in any page list puts one more page beside everything already on screen — as many as the screen fits, each with its own **✕** , each able to leave for a window with **⤢**. It is a second verb rather than a change to the one you have: **⇄ Open Beside This Page** is still the single reading pane that holds a PDF, a book or a canvas, and an extra pane holds a page. Ask for one twice and you get the pane you already have, not two columns of the same words. - **The split pane pops out.** **⤢** in its header turns the pane into its own window, which is what a wide screen wants: the pane is one more page, a window is as many as the screen holds. - **Write in several sources as one answer.** _Insert from Your Sources…_ has always written a paragraph about each ticked paper in turn, which is right when the ask is about each paper and cannot answer an ask about the set. **Write them in as** now offers _one answer about all of them together_ — a comparison, a table of methods, a list in a style we do not ship — with every source labelled so the answer can say which is which, and all of them linked underneath. Each source’s share of the reading shrinks as more are ticked; where that would leave too little of each to be reading at all, the ask is refused with the number that would work. - **A paper’s number in the Info pane is a link.** A DOI, a PMID or a PMCID listed under Aliases opens the registry’s page for it; right-click for the link or the identifier itself. - **The view column called Type is now called Format** , and shows the words the rest of the app uses — _Formatted text_, _Markdown_, _Canvas_ — rather than the value underneath. Three columns could be read as “type” and this was the one that meant none of the things people reached for it for. Views you have already saved go on working, including ones written against the old spelling. - **An empty database view says why it is empty.** A filter on a column that no page in the wiki fills could never have matched anything, and saying “loosen a filter” about one of those sends you off to widen a condition that was right. It now names the column — and where the value you typed is a **Kind** rather than a **Page type** , it says so and tells you which column to use. **Fixed** - **Settings ▸ Editing: the heading sizes are readable again.** The six boxes had their captions — H1 to H6 — written as plain words rather than as labels attached to the box each names, so the card’s layout swept the boxes to one side and left the words behind them, overlapping. They are labels now, which fixes the overlap and gives six number boxes the names they never had for a screen reader. The same repair reaches the custom paper **Trim** row, and the backups folder field. - **…and the numbers in them are not cut off at the larger interface sizes.** Those boxes were a fixed width in pixels while every font around them grows with **Interface size** , so at _Roomy_ a value like `0.95` did not fit. They are sized in step with their own text now, at every interface size.