Skip to content

0.2.3

Choose a tag to compare

@github-actions github-actions released this 02 Aug 23:15
f1cd823

Four fixes to things you touch with the mouse, all found by playing a feature by hand before filming it rather than by a report.

Fixed

  • Colour pickers open the way Obsidian's own does. Every colour control was an invisible <input type="color"> inside a <label> that activated it — and opening its popover from the settings window emptied the settings pane behind it, leaving the tab selected with nothing in it until you clicked it again. Obsidian's accent-colour setting, which behaves, is a plain visible input; ours are now the same thing, shaped into the same circles by CSS. Three places: the palette in Settings → Custom colors, a field's picker, and the canvas colour options
  • The icon picker shows the icon you already have. It renders 240 of some 1900 icons in alphabetical order, so a field holding rocket opened on a screen starting at a-arrow-down with nothing saying what the value was — you had to search for what you already had in order to see it. The current icon and its id now sit above the search box
  • The coordinates box reads what you actually paste. It accepted the canonical lat,lon and nothing else, and said nothing when it refused: a Google or Apple Maps link, an OpenStreetMap link, a geo: URI, a degree-marked pair like 48.8584° N, 2.2945° E, even a space between the two numbers all filled nothing at all. All of those are read now; text that holds no pair says so, and a pair that is off the globe is told apart from one that couldn't be read
  • The "Set next date" button had no label. setIcon() on an Obsidian button replaces its content, so the text set just before it never rendered: the date picker showed an icon with no name, nothing on hover, nothing for a screen reader. It reads Set next date again

Learning the plugin

Five new takes, one per field type, on the pages that describe them: templated input, dates that link to your daily notes, icons, colours and your own palette, and a place on a map — the last one ending on the Maps plugin, where a Location field, an Icon field and a Color field turn out to be exactly the three properties a map marker needs.

Twenty-two videos now, forty-eight minutes: https://mdelobelle.github.io/fileclass/videos/

Compatibility: minAppVersion 1.12.7. Fileclass builds on the core Bases plugin, which needs to be enabled.