Mavericks Finder - how default to "double click opens new window"?

The only way I've found to do this, is to highlight the folder (that's inside another folder) and then go to "Action" in the folder toolbar. Click it. Then, hold down the OPTION KEY, and where it said, "Open Folder in New Tab" will now change to "Open Folder in New Window". Click it and your folder will open in a new window and the original folder window will still be there, too. (Whereas if you do not go thru the "Action" button to do this, but instead just hold down option while clicking to open the folder, the "original" folder will automatically close itself -- VERY Maddening!!) What the heck was Apple THINKING???

OH, HEY!! I just now figured out that I can avoid SOME of the above... Highlight the folder (that's inside another folder) and then click on ACTION in the folder toolbar. Scroll to very bottom and it says "Open". Click that and it open in another window and the original folder window stays there!!

STILL not as "easy" as it used to be, but at least "doable".

Message was edited by: AppyHorsey

If you open a folder, let's say "Macintosh HD" you will notice that it will open with Two Toolbars. One on the left, and one on top. If you right clic on top of the window and select "Hide Toolbar", it will make this two Toolbars disappear. After that, every new window you open that is inside that folder will open on a new window.

I think that can fix the problem.

Unless, of course, you want to keep the ToolBars.😢

albabe Al Gordon wrote:

Unless, of course, you want to keep the ToolBars.😢

And, personally, I do NOT want the ToolBar at the top. I'd love to be able to suppress the ToolBar globally. Is there a preference to "always hide" the ToolBar?

Actually... The REAL point to me here is... Why can we "Open New Folders in New Windows" in one mode and not the other? Why did the Authoritarian Designers at Apple make that decision? That seems really weird to me.

The point to the whole thing is that I'm usually up for every change that "improves" the experience. And I know that you cannot keep every little functionality since Tiger, for example, and that some things, have to be removed to keep going forward.

But sometimes companies just remove features out of the blue, and force the user to re-make a new workflow based on the new/changed features.

Handling windows opening, closure, and that in OSX since Tiger never changed until now. That's a lot of years of user experience you are negating with this design decision.

For me, it would have been nice to put the actual windows management as standard configuration, but leaving the user to change back to old management system. That way you are showing that you think the new way is better, and that this feature will probably be removed in future versions.

Anyway, I know it's a pain in the ***, but I'm pretty sure that there has to be some script or way to revert that behaviour. And if there's not, you, like me, and the rest of people will have to get along with this.

Sadly, it's not just automatic behavior that started with Tiger. If I am not mistaken, the behavior of opening windows in a new window has been around since the original Macintosh, and even the LISA that preceded the Mac!

And yes, that means it worked that way (I believe) in the Macintosh File System (MFS), the Hierarchical File System (HFS), and everything since.

The point is that for decades this communication between human and machine has been natural, intuitive, and reinforced by practice for decades. Apple changed it seemingly for no reason. Perhaps it's to mimic the behavior of an iPad or an iPhone (I don't know, since I own neither).

Worse than that, the new process actually makes us work harder! Pre-Mavericks, we were able to choose with keyboard selections whether to open windows in a new window or replace the window with the new window. There were times when I did both, although the latter most frequently. Now, I am forced to use only one method, which has me working harder.

The Macintosh became dysfunctional in yet another way. Yes, it reminds me of what Microsoft would do with Windows, like remove the Start button.

Just a little FYI:

I finally got Helgason'scool EasySIMBL TheLostFinderNewWindow to work. As far as I could tell, I had it installed correctly and even turned-on, but I wasn't having any luck and eventually just gave up and assumed I'd have to follow Apple's Brown-Shirted, Mandatory IOS Interface Dictates...

A couple of days ago, just on a Lark, I went to Helgason's original post here with his D/L page, and re-downloaded it, thinking it might possibly have been Updated. It had the same Version Number but I dropped it into EasySIMBL and EasySIMBL asked if I wanted to replace it - I said Yes and rebooted, and now everything works completely groovy!

I was starting to get used to the Window-In-Window Neo Apple Authoritarian Mandates, and now (at least for the time being), I don't have to - Now I need to get used to using my Windows the way I've always done it and liked. Ah, the crushing Irony.

PS: What can I say - I'm a curmudgeon - I'm still annoyed that Apple dropped the Windowshade function from OS9... sigh.

Agh, Apple, why do you keep removing UI features & options?!? How does this make things better?!?

Scroll bar arrows...now I can't default double-click to mean "open folder in new window"! Argh!

I'm having another issue: I resized a window and now all windows are that size. How do I reset the window size to defaults?

The vandals at Cupertino fiddle aimlessly with the finder and with other elements of the Macintosh computer’s operating system while the Apple empire’s credentials burn.

That's the best laugh I have had in a while

Thanks for your humour.

Alas, if you don't open in a new window, all windows you open become the size of the one you started from. If you revert to old style windows without the task bar to recover double click window opening, then everything stays the side you had it. Also, if you keep the new style window and open up with the option button command, it will come up the size you had it.

I already reported that **** behavior using Apple's Feedback Utility in the OS X Beta Seed Program.

I suppose you're answering on my question? Sorry, but I don't fully understand your explanation.