-
-
Notifications
You must be signed in to change notification settings - Fork 30
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 Pane Won't Close #109
Comments
Hmm so seem to have narrowed this down a bit. This seems to only occur when one of the items is a pinned item in Obsidian. If you unpin the item to the left, then things work fine and the panel to the right will close. Repinning does not trigger the malignant behavior thankfully. |
Hi Grant (gwillcox-r7), I'm facing exactly what you described. Is this a bug or expected behavior of the plugin? Thank you |
i am too facing this bug when i updated this plugin today, i reverted back to the release 3.2.3 manually to get rid of this bug. |
Same bug here also same details as gwillcox-r above |
I believe this is new, it didn't act like this before from what I can tell and @Vichu-dev's comment suggests this is a regression. |
Can you please tell me if you can get back to normal after reverting to version 3.2.3? |
Yes, I'm facing the same issue. At the very moment that the plugin is enabled, it creates an empty pane which is impossible to get closed. Obsidian.-.Sliding.panes.mp4This happens if all the open panes were pinned. If any open tab gets unpinned, then makes it possible to close such an empty pane. For doing this video testing, ALL other plugins were turned OFF, and Obsidian was also restarted. I'm using the latest versions, that is: This behaviour makes it pretty uncomfortable to deal with the panes. Please correct it if possible. Thanks! |
I've come here after experiencing the same issue myself. I've dug into the Sliding Panes source a bit and found the cause of the issue. This is caused by calling sliding-panes-obsidian/src/main.ts Line 262 in 8e91d95
The active leaf is used when deciding if it should be focused when it is currently in the active container. sliding-panes-obsidian/src/main.ts Lines 324 to 325 in 8e91d95
I'm not sure why this is done, seems to be related to Obsidian popout windows. I've been using a modified version of the Sliding Panes plugin with those bits of code removed without noticing any issues. |
@torves |
I would suggest reverting back to 3.2.3 release manually and see if the bug is fixed, before trying the code deletion method. |
Hello torves, Thank you very much for your tip, it worked smoothly. I edit the file "main.js" in sliding-panes-obsidian directory and added "//" in front of "workspace.getleaf"... the code line in my file was not exactly the same as your code but searching by "workspace.getLeaf" was enough to find and neutralize the codes |
I would like to share what I did to fix the problem based on the @torves' comments (thank you very much) I was suspicious of the possibility to lose the content of the "today's daily notes"... now I'm sure that it doesn't happen. 01 - go to the Obsidian plugin folder I hope those steps could help someone |
I tried your method with Notepad and it solved the problem of not being able to close blank windows perfectly and without any file loss! Thank you very much for your help! |
Hello @MILKMILKKING, I'm glad to hear that!! 😀😀😀 |
hahaha, Obsidian v0.16.0 has just been released and changed everything. |
Well Obisidian 0.16.2 just introduced tab stacks which should essentially offer most of the same functionality as this plugin. I'll leave this issue open but if anyone is looking for an intermediate solution in the meantime this may be something to look into. |
When opening certain panes a new blank pane will open. If I try to close that pane, now it will continuously open that pane again....and again....and again. Its now impossible to close that second pane down so I'm left with a screen that constantly looks like this:
This seems to have only occurred after I updated to the latest plugin version aka 3.3.0 about 2-3 days ago.
The text was updated successfully, but these errors were encountered: