[Bug]: Drop lines in file explorer seem offset right

[olearydj]

Bug Description

With Obsidian v0.15.6, SF v7-13, Style Settings 0.4.10, the "drop lines" in the core file explorer plugin appear to be rendered to the right of the expected position.

Relevant Screenshot

To Reproduce

Open the core file explorer and observe the line placement.

Obsidian Version

0.15.6

Installer Version

0.15.6

Font Size

16

Which editor are you using?

• [X] New Editor
• [ ] Legacy Editor

In which mode(s) does the problem occur? (if applicable)

• [X] Source (Edit)
• [X] Reading (Preview)
• [X] Live Preview

Which operating system?

• [X] macOS
• [ ] Linux
• [ ] Windows
• [ ] iOS
• [ ] Android

Plugin-Specific Problems

• [X] I took note of the specific instructions regarding those plugins.

Checklist

• [X] I updated to the latest version of the theme (Settings → Appearance → Themes - Manage → Update).
• [X] I made sure that the issue is related to this theme by checking that the problem does not occur with the default theme.
• [X] In case I am missing an UI element, I have checked that it cannot be re-enabled with the Style Settings plugin.
• [X] If the bug occured after updating the theme, I read the last couple of entries in the changelog to make sure the bug is not an intentional change. (In that case, there will most likely be a style setting to turn it off again.)

[olearydj]

I realized this morning that the problem goes away if I re-enable the folder icons (off by default) in the file explorer.

[chrisgrieser]

Hi! As you may have heard, the upcoming Obsidian update 0.16 has a massive amount of changes for theme development, necessitating a complete rewrite of Shimmering Focus. This means:

1. A lot of bugs and feature requests will be obsolete. with Obsidian 0.16 and the rewritten Shimmering Focus.
2. As the theme has over 15,000 lines of CSS, the rewriting will take a considerable amount of time. Recreating the core features alone will likely take me a while, so I simply will not have much time to implement many feature requests, since the recreation of the past core features has priority.

Basically, this is the reason why I am – for now – closing this issue. If your bug still exists / your feature request is still relevant in the upcoming version 3.0 of Shimmering Focus, please comment here and I will re-open it. 🙂