joplin-plugin-cockpit 2.6.0 → 2.6.1

package/README.md

@@ -132,6 +132,8 @@ When a search matches nothing inside the current filters, Cockpit runs one unfil
 
 Excluded notebooks are named in the settings, and are hidden from Cockpit everywhere — search results, panel rows, checkbox counts, the overview notes and the notebook picker — sub-notebooks included. Entries are resolved to notebook ids and tracked by id, so renaming or moving an excluded notebook keeps the exclusion working, and a Parent/Sub path disambiguates notebooks that share a name.
 
+The field shows both halves of what it points at — `Lab / Joplin (fdfd6c06), Archive (a1b2c3d4)`: the name you recognise, and the short id Cockpit is really tracking, so a setting aimed at the wrong one of two same-named notebooks says so at a glance. You go on typing whatever is easiest — a name, a Parent/Sub path or a full id — and Cockpit rewrites each entry into that form. A name it cannot match is left exactly as you typed it, with no id, so a typo stays visible. Where the id is the part that still matches (you renamed the notebook in Joplin and never re-typed the setting), the id wins and the name shown catches up. A notebook genuinely called `Budget (deadbeef)` is not mistaken for one: brackets are read as an id only when what is in them is the start of an id that exists.
+
 An excluded notebook can never become the panel's notebook filter, by any route: not from the dropdown, which does not list it; not from another plugin's command, which is refused with a notice; and not from a profile that stored it before it was excluded, which starts at "All notebooks" for the session while keeping its own saved notebook untouched. Exclude the notebook the panel is currently filtered to — or delete it in Joplin — and the filter returns to "All notebooks" on the spot. This is also why New note and New to-do ask where to create whenever the header says "All notebooks": the filter and the label can never disagree.
 
 The notebook dropdown lists every notebook by its full path, with a filter box pinned at the top; typing narrows it and Enter picks the first match. It offers every notebook, not only the ones the current to-dos live in. Every row also carries the notebook it lives in: click that pill to filter to it, right-click it to move the note somewhere else, hover it for the full path.
@@ -208,11 +210,13 @@ Joplin syncs notes, never plugin settings, so profiles normally have to be built
 
 Setting it up is one field, and it is the same field on every platform. Open **Settings › Plugins › Cockpit** and type `Joplin Cockpit Plugin Settings` into **Settings note**.
 
-- On the **first device**, no such note exists yet, so Cockpit makes one: a note of that name in the notebook you are looking at, filled with this device's profiles and settings, with the field rewritten to the note's id.
+- On the **first device**, no such note exists yet, so Cockpit makes one: a note of that name in the notebook you are looking at, filled with this device's profiles and settings, with the field rewritten to the note's name and short id.
 - On the **next device**, sync first so the note arrives, then type the same title there. Cockpit connects to it, and any profile that device has which the note does not (by name) is added to the note rather than lost. Pasting the note's id or a link to it does exactly the same.
 
 Type the title before the note has synced down and the second device makes a note of its own, because there is nothing yet to find. Cockpit watches for that on the next few syncs and tells you when a second note of that name turns up, so you can paste the id of the one you want to keep into the field. Syncing first avoids it entirely.
 
+Copying the first device's field text across instead — `Joplin Cockpit Plugin Settings (310b413d)` — never makes a second note, even before the sync: that text can only have come from a note that already exists, so Cockpit says it cannot find it yet and connects the moment it arrives.
+
 There is also a `Cockpit: Connect settings note` command in the command palette. It is the same three steps and the same rules; the field is the one to reach for.
 
 What travels: your profiles, the custom panel CSS, the theme and its colours, the completed-to-do style, the day start time and the excluded notebooks. What stays per device: the font and circle sizes (a phone and a 27-inch monitor want different ones), the refresh interval, the toolbar button, the two title-bar options, and which profile is currently selected.
@@ -260,8 +264,8 @@ Cockpit's settings live in Joplin's own Settings › Plugins › Cockpit.
 
 - **Panel refresh interval** — how long Cockpit waits between background refreshes of the panel and the overview notes. 60 seconds by default on desktop, raised on mobile unless you set it yourself.
 - **Day start time** — the time a to-do gets when it is dragged onto a day it has no time of its own for. 09:00 by default.
-- **Excluded notebooks** — see [Search and filtering](#search-and-filtering).
-- **Settings note** — type `Joplin Cockpit Plugin Settings` here and Cockpit creates that note, or connects to the one that has already synced in from another device. A note id or a link to it works too. Empty by default, which keeps everything on this device. See [Sync your settings between devices](#sync-your-settings-between-devices).
+- **Excluded notebooks** — the notebooks Cockpit hides everywhere, typed as names, Parent/Sub paths or ids and shown back as `Name (id)`. See [Search and filtering](#search-and-filtering).
+- **Settings note** — type `Joplin Cockpit Plugin Settings` here and Cockpit creates that note, or connects to the one that has already synced in from another device. A note id or a link to it works too. Once connected the field reads `Joplin Cockpit Plugin Settings (310b413d)` — the note's name and the first characters of its id, which is how Cockpit tells two notes of the same name apart — and follows the note if you rename it. Empty by default, which keeps everything on this device. See [Sync your settings between devices](#sync-your-settings-between-devices).
 - **Theme, completed-to-do style, font size, circle size and the six custom colours** — see [Appearance](#appearance).
 - **Show the Cockpit button in the note toolbar** — a gauge button in the note toolbar toggles the panel, and the same command sits in Tools › Cockpit alongside this switch and Set Panel CSS, with **Ctrl+Shift+H** as its keyboard shortcut on every desktop platform (change it under Options › Keyboard Shortcuts). Joplin cannot add or remove a toolbar button while running, so turning it on or off applies after a restart, and Cockpit says so.
 - **Hide the due date next to the bell in the note title bar and show it on hover** — when a to-do has an alarm, Joplin prints the due date as text beside the bell in the note title bar, and that text eats the space the title has. With this on, the text is hidden and appears as a small bubble under the bell while the pointer is over it. Desktop only. Off by default. Joplin cannot unload a stylesheet it has already loaded, so this applies after a restart.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "joplin-plugin-cockpit",
-  "version": "2.6.0",
+  "version": "2.6.1",
   "description": "A tasks-and-notes command center panel: due dates with drag and drop and a calendar picker, checkbox progress rings, notebook and search filters, view profiles, and notebook management - on desktop and mobile.",
   "repository": {
     "type": "git",

package/publish/io.github.pmslava.cockpit.json

@@ -7,7 +7,7 @@
 		"desktop",
 		"mobile"
 	],
-	"version": "2.6.0",
+	"version": "2.6.1",
 	"name": "Cockpit",
 	"description": "A tasks-and-notes command center panel: due dates with drag and drop and a calendar picker, checkbox progress rings, notebook and search filters, view profiles, and notebook management - on desktop and mobile.",
 	"author": "pmslava",
@@ -43,6 +43,6 @@
 			"label": "The alarm picker: ISO date, 24-hour time, a Monday-first calendar, and quick shortcuts"
 		}
 	],
-	"_publish_hash": "sha256:cb5c0e96dfd047b1357314ae4152dd2c1545e57677225ef5fdff82ea7fcfa5ab",
-	"_publish_commit": "master:41334aa3b26e8726706844ab123285cb573e8db4"
+	"_publish_hash": "sha256:0fd053462ff074dcec75913c963dbebfdc5e173fad6809b21a1e8715a5dfd704",
+	"_publish_commit": "master:cb57505b1958f9858cef764989ed63edef62273f"
 }