Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sliding Panes Nonfunctional With Many Panes #114

Open
julroger2013 opened this issue Jul 25, 2022 · 5 comments
Open

Sliding Panes Nonfunctional With Many Panes #114

julroger2013 opened this issue Jul 25, 2022 · 5 comments

Comments

@julroger2013
Copy link

In the most recent version or two of Obsidian's Insider Build (0.15.8, presently) Sliding Panes malfunctions when working with many panes.

I recently attempted to open a total of 9 panes (one writing project and 8 associated source notes), with the idea that I would use the Pane Relief plugin to switch between panes as needed for references purposes (e.g. alt + 9 to access the 9th pane). And I did so while using auto-leaf width in sliding panes.

The idea was that I would freely swap between full size panes for any of the open notes by invoking the relevant hotkey. But unfortunately certain panes (it seems random which ones) will either open blank or, when focused, will not autoscroll to being at the center of the screen, as I would have expected. It might autoscroll halfway on to the designated note, or it might not scroll at all.

This was a real bummer, to be honest. Your plugin has become one of my favorites because it makes workspaces with many documents more feasible to work with.

In any event, I don't know if the iteration of the issue that I'm seeing (difficulties with autoscrolling when many panes are open) is distinct from the issue reports I've seen relating to auto-width more generally, or if it's all part of the same thing.

Thank you for making this wonderful plugin!

@kithairon
Copy link

kithairon commented Jul 28, 2022

Similar experience as OP. Saved workspaces with 6-12 panes that used to open at a pinch and be working fine with Sliding Panes erratically fail to load since a recent update – they sometime load as empty panes, don't slide anymore etc. Starting the app anew may resolve the issue temporarily. Opening individual new panes (rather than via the saved Workspaces plugin) seems to work fine.

I'm writing in much the way the OP described on notes with a number of sources open at the same time. I save all of these as a workspace and reload the latter when I continue writing after doing many other things as more of my digital life has moved into Obsidian. I have come to appreciate Sliding Panes as a deeply useful way of moving between my writing and collected source materials.
Things I have tried with no effect: changing to default theme, disabling all other of my plug-ins (including Pane relief), uninstalling Hover editor plug-in (this used to cause similar issues with Sliding Panes at some point last spring). Things that occasionally helps: re-starting app.
Your plug-in and the possibility of stacked and/or sliding panes is ingenious and brilliant.
Thanks for looking into the issue.
Obsidian Insider v0.15.9 / installer 0.15.6 | macOS 12.5

@kithairon
Copy link

Tested with previous version of Sliding Panes (v3.2.5) All of the above issues described in my prior post are absent and the plugin seems to work flawlessly on my system. Will stay on v 3.2.5 for the time being. Happy to help debugging a new version. Grateful for your work.

@ebullient
Copy link

Related to #110, I think. Last group of fixes to adjust how width was set I think missed some nuance. Maybe that needs to be backed out, and changes constrained to just those dealing with changes related to popout windows...

@stoweboyd
Copy link

I also have encountered this issue.

@stoweboyd
Copy link

stoweboyd commented Aug 28, 2022

It has been a month since I added a comment here about Sliding Panes becoming unresponsive with many panes open. I used BRAT to revert to an earlier version, but I am hopeful that the additional functionality in 3.30 will be accessible to me soon. But there doesn't seem to be any response from @deathau about these issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants