![]() I have implemented an escape hatch for people who want to opt-out. ![]() It just sees new Finder browser created and at that point can decide to capture it. TotalFinder does have knowledge of the reasons why new Finder window is being opened and who and how originated it. There is one exception, in case of a DMG file, TotalFinder lets Finder do its normal job and does not capture. Finder file browser instance could be a new Finder window or a new native Finder tab - depends on your Finder settings and macOS version. Under normal circumstances TotalFinder tries to “capture” all new Finder “file browser instances” and convert them into tabs. Ok, let me chime in with some explanations. That is, whether TotalFinder is running or not, and whether Visor is running or not, the New Finder Window command will actually open a new Finder window. My limited testing shows that in Sierra and El Capitan, New Finder Window works as expected. If you kill the TotalFinder processes, New Finder Window does work. The difference is that if Visor IS running, then the New Finder Window command will open a new Home tab in the Visor window. Whether Visor is running or not, makes no difference. ![]() In High Sierra, New Finder Window does not work at all if TotalFinder is running. ![]() This is new behavior, and appears to have started when I installed High Sierra a couple of weeks ago. There does not appear to be a way to actually open a new Finder window. Likewise, Finder -> New Finder Window no longer opens a new window, but only a new Home tab in the Visor window. Whenever I type Command N Visor opens with a new Home tab. Makes no difference whether ‘Freelance Windows’ is checked or not. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |