Locking the tree causes "zombie" root node tab on startup with path argument.
Locking the tree causes "zombie" root node tab on startup with path argument.
Tree unlocked:
"XYplorer.exe" - works fine
"XYplorer.exe C:\" - works fine
Tree locked:
"XYplorer.exe" - works fine
"XYplorer.exe C:\" - zombie root node tab that's always there as first tab and the actual path I pass is second tab.
"XYplorer.exe" - works fine
"XYplorer.exe C:\" - works fine
Tree locked:
"XYplorer.exe" - works fine
"XYplorer.exe C:\" - zombie root node tab that's always there as first tab and the actual path I pass is second tab.
Re: Locking the tree causes "zombie" root node tab on startup with path argument.
Can you at least provide the version number you're using and in this case two screenshots, one for both scenarios?
I can't see any difference when trying this with a fresh v22.30.0101 instance with unlocked / locked tree...
I can't see any difference when trying this with a fresh v22.30.0101 instance with unlocked / locked tree...
One of my scripts helped you out? Please donate via Paypal
-
- Site Admin
- Posts: 60601
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: Locking the tree causes "zombie" root node tab on startup with path argument.
Might be related or not, but looking into this I found a bug (and fixed it):
Code: Select all
! Configuration | General | Startup & Exit | Open command line start path in
new tab: The unticked state was not completely honored. Fixed. Now when
unticked the current tab is overwritten by the command line start path
unless the tab is locked.
FAQ | XY News RSS | XY Twitter
-
- Site Admin
- Posts: 60601
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: Locking the tree causes "zombie" root node tab on startup with path argument.
So by "zombie" you mean "new".
Should be fixed in next beta.
Should be fixed in next beta.
FAQ | XY News RSS | XY Twitter
Re: Locking the tree causes "zombie" root node tab on startup with path argument.
What I thought to be a bug was actually an option I didn't even know existed which was itself bugged. Not the unticked state wasn't working correctly as you mentioned, but the ticked one cause that's what I had. Still bugged in v…102 btw (same different behavior with locked/unlocked tree). I'm not sure what exactly was "fixed" but if I'm right this time, the next step should be to "unfix" it and fix the real bug.
-
- Site Admin
- Posts: 60601
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: Locking the tree causes "zombie" root node tab on startup with path argument.
Still bugged? Works fine here. What exactly is not working as expected?
FAQ | XY News RSS | XY Twitter
Re: Locking the tree causes "zombie" root node tab on startup with path argument.
It still works for me like on the .gif above.
"Open command line start path in new tab" if ticked doesn't work with the unlocked tree.
"Open command line start path in new tab" if ticked doesn't work with the unlocked tree.
-
- Site Admin
- Posts: 60601
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: Locking the tree causes "zombie" root node tab on startup with path argument.
So you WANT a new tab and your tree is UNLOCKED? That's the opposite from your first post. But anyway, it works fine here.
FAQ | XY News RSS | XY Twitter
Re: Locking the tree causes "zombie" root node tab on startup with path argument.
Currently I don't want anything. The behavior I wanted was available from the very beginning through unticking the option I didn’t know existed.
If what you see on the .gif is not a bug, then let it be as it is.
If what you see on the .gif is not a bug, then let it be as it is.
-
- Site Admin
- Posts: 60601
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: Locking the tree causes "zombie" root node tab on startup with path argument.
It's not a bug if Configuration | General | Startup & Exit | Open command line start path in new tab is ticked.
FAQ | XY News RSS | XY Twitter
Re: Locking the tree causes "zombie" root node tab on startup with path argument.
Thank you anyway! Sorry for wasting your time...
-
- Site Admin
- Posts: 60601
- Joined: 22 May 2004 16:48
- Location: Win8.1 @100%, Win10 @100%
- Contact:
Re: Locking the tree causes "zombie" root node tab on startup with path argument.
A fixed bug is never a waste of time.
FAQ | XY News RSS | XY Twitter
Re: Locking the tree causes "zombie" root node tab on startup with path argument.
Sorry for bringing it up again. Please tell me what I'm missing. The whole point of "Open command line start path in new tab" is to prevent overriding of current tab if the app is running. But if it isn't running, there is no current tab and nothing to override. So if I provide a path, I want this path as first tab. Why do I get "This PC" as first tab instead? And even more importantly, why does this behavior only occur after locking the tree?
Re: Locking the tree causes "zombie" root node tab on startup with path argument.
PS. The only way current tab exists when the app is not running is if this is ticked:
But if the app is not running and the option is unticked, it doesn't make sense to create another tab. First tab IS the new tab already. Unlocked tree knows that and works perfectly fine. The bug must be the missing check of this option on startup for the locked tree case.
Code: Select all
Include most-recently-used lists on save [Startup & Exit - Save Settings]