Page 2 of 2

Re: Locking the tree causes "zombie" root node tab on startup with path argument.

Posted: 01 Nov 2021 09:26
by admin
Evolve wrote: 31 Oct 2021 08:56... The whole point of "Open command line start path in new tab" is to prevent overriding of current tab if the app is running.
No. The whole point of "Open command line start path in new tab" is to prevent overriding of current tab if the app is NOT running. Hence the name.

Re: Locking the tree causes "zombie" root node tab on startup with path argument.

Posted: 01 Nov 2021 09:35
by admin
Evolve wrote: 01 Nov 2021 05:47 PS. The only way current tab exists when the app is not running is if this is ticked:

Code: Select all

Include most-recently-used lists on save [Startup & Exit - Save Settings]
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.
Indeed, the relation to "locked tree" is strange. I'll look into this.

Re: Locking the tree causes "zombie" root node tab on startup with path argument.

Posted: 01 Nov 2021 10:03
by admin
OK, next beta should fix it.