@SamAdams you’re welcome, Sam. I have not come across a community like the Obsidian community before. 99% of the people are friendly and helpful, and there are some amazing experts among them. If you go to the Discord #appearance channel and ask questions there you’ll soon encounter them.
Cheers.
1 Like
Ok, thanks for the tip on the discord channel.
1 Like
Super handy plugin!
Slight UI improvement request: allow the text boxes to expand with the width of the settings window. Right now, even if Obsidian and its settings are fullscreen, the text boxes in Style Settings (such as in the Font section) stay super narrow, which makes them difficult to check at a glance and edit quickly. Narrow boxes work well with a narrow window, but when the width is available, it would be great to take advantage of it!
Thanks so much for this must have plugin ! Do you think it could be possible to assign keyboard shortcut to class-toggle elements ?
I can’t seem to find the snippet for the custom background in your github, i’m not too familiar with github so that might be my problem but could you tell me where exactly the custom background snippet is?
Yes, it’s a little confusing. 
If you click in the box (or circle in my case - it depends on your theme),
you’ll get this pop-up to choose the color. Manually type in the HEX/RGB vaule or click in the color selection area → Save. Your choice should be saved.
The back arrow resets to it to the default value, so no worries!
I never thought that a plugin like style settings could have such a impact on how we can use Obsidian.
At first, curiosity pushed me to try some themes, but I didn’t see any value in colour plays - so, this plugin was nothing essential to have, no plugin to care for.
Only developing CSS code brought me back to reconsider style settings to add features in addition to color plays. Style settings turned from a “apparently insignificant” plugin to a “must-have” plugin.
With the latest release of Obsidian v1.7.4, (or v1.7.5) style settings broke, the latest update was 3 months ago.
The switch from dark to light or vice versa, makes my theme transparent and kind of, melts fonts - only reloading solves this issue temporarily but doing this repeatedly is no method, at least not for me.
Today I reverted Obsidian back to 1.6.7, first time I do something like this for a plugin.
I’m still wondering why a plugin can have such an impact to roll back one version, as plugins should be secondary to an application.
There are a ton of themes available for Obsidian, all thanks to Mgmeyers’ plugin - that’s amazing.
I think it’s high time to incorporate style settings as a curated core plugin into Obsidian, popularity and usefulness of this plugin tells.
I did the opposite.
Disabled the plugin and whatever was used through it is used via css snippets.
Can’t, because the harsh black and white default theme isn’t acceptable to me, furthermore I extended the feature palette in Obsidian to meet my needs.
Feel free to check out my wiki docs on Obsidian-Dune84/Wiki at main · Jopp-gh/Obsidian-Dune84 · GitHub
My problem was from before Obs. ver. 1.7.
Generally slow UI experience, tab opening and closing lags, etc.
Other people complained as well:
Btw, as someone handy with CSS, why not build on the default theme.
The Minimal theme has a separate styler plugin, I don’t know how that fares in 2024 last quarter.
I don’t know the author of Aura, nor his/her coding style.
Maybe this theme calls some heavy rules and / or this code wasn’t optimized for less powerful computers and / or the code is simply outdated. Important to remember, old plugins or themes cause always some delay, because of errors. Some errors are insignificant, but bigger errors are less “ideal”.
I’m my opinion, Mgmeyers build a lot of fine and popular plugins, he’s clear how to write code, updating and sharing his passion with some regularity, so my guess is that aura would need a check.
Yes, I totally agree with you, speed is very important, lame apps are very frustrating. I didn’t experience a slow Obsidian so far, the 3+ years long.
My only complaint was that obsidian mobile did reload very often before v1.7.x. Meanwhile, obsidian mobile got a nice boost and reloading has been resolved, IMO. I’m happy about the last developments.
The desktop version was always speedy, since I used Obsidian. Usually I keep my plugins very low, not just because I want future proof documents, but also because I build my own scripts if I need a plugin. They’re not in typescript, so these scripts can’t be shared - I’d have to learn typescript first.
I’m sure the other posters on that issues thread were not using Aura, so it is largely irrevelant.
It was relatively easy to unlink my Supercharged Links rules from Style Settings and link them with a CSS snippet, so far as I’m concerned, it’s smooth sailing from this point on.
…Seems like the author of the plugin is otherwise engaged.
Nice talking to you, mate!