Sorry all, I've been working 12 hours straight for the last 3 days.
Screw auto quitting apps.
On Apr 30, 2012, at 3:21 PM, Nick Zitzmann wrote:
>
> On Apr 28, 2012, at 2:22 PM, Alex Zavatone wrote:
>
>> DAMMIT. Xcode auto quits in Lion after you close all its windows and click away from the app.
>>
>> How the hell can we turn this off?
>
> You can't.
Screw it. If I can't find a way to return the old Mac experience, then I'm simply making my money and getting out. If this is the new Mac, then seriously, the Mac is dead to me, this is not pleasant.
What is it? NSSuddenTerminationDisabled? Something like that? I was able to recompile TextEdit, rename the bundle and set the "I know better than you, so I will quit for you" setting to #DIE_IN_A_FIRE.
>> Lion is simply horribly annoying x10.
>
> Well, I like it better. I didn't appreciate the removal of iSync at first, because at the time I was using a phone that didn't support networked contacts or calendars, but then I switched phones and got over it.
CASE IN POINT.
We had scroll bars that tell us what is scrollable without us having to interact with the screen.
NOW, we have windows where the content bounces to tell us that "hey look, I can scroll" AFTER YOU'RE DONE SCROLLING to the end of a scroll region you KNOW you can scroll in. Even if "always show scroll bars" is on.
So, think about it. IF scroll bars are off, you have to interact with a part of the screen to see if it's scrollable. This is fine on an iDevice, but not on a computer that has enough real estate to show scroll bars. This is less effective than simple disable scrollbars.
Also, IF scroll bars are on, you know you what is scrollable by... wait for it... LOOKING AT THE SCREEN! WHY are the scrollable regions elastic when you already know you can scroll?
In Safari, without a window that has no scrollable content, if you mistakenly do a drag past the window, the whole content of the window shifts, as the view separates from the bounds of the view and then pops back when you release the mouse.
But in this case, the window is NOT scrollable, so the view should NEVER be telling me that it could scroll, because it CAN'T. Why do this? It's irritating to see my content leave the bounds of the scrollView, especially with no way to turn it off.
Now, if you like Safari, and you download stuff, the downloads window is no longer a window, and it is no longer able to be opened if there is nothing in the downloads queue. The menu item is conditionaliy disabled. Ohhh, I know better than you and you didn't want to see an empty non window anyway, so I'll turn this off. Sweet mother of aggravating. It's high on the annoying level when you press a command key (command opt L) and nothing happens.
>> Guys, I WANT to use the GUI of the app to open files. This is how many people actually navigate to the projects they use. Each app REMEMBERS the files and folders where the user has navigated. This is WHY we use the open dialog in applications. When we nav away from the app, we want it to be there when we get back.
>
> Define "many." I just use the Finder and Spotlight to open files in apps. To me, the "open" command often feels like a leftover from Mac OS 6, where it was the only way to open a file without relaunching the app if multitasking wasn't turned on.
If you use the Open dialog, you qualify as one of the many.
>> Why are you doing this to us? This kills the user experience of using a Mac.
>
> Because the general public has spoken: They prefer not to manually manage their computer's memory usage. You are the exception. Windows and X11 apps auto-quit once their last window has been closed, Android apps auto-quit once they've been left idle in the background for a while, and I think we all know about how iOS handles this.
The simpletons have spoken? People too lazy to quit apps? Or is it just people who are used to Windows?
> So I'm willing to make an educated guess that many Mac users just left apps open all the time, then complained to Apple or third parties that their computer was now slow, since they hadn't been trained to manually manage their running apps. And unlike Mac OS 9 and earlier, the OS doesn't force users to manually manage their apps by refusing to launch new apps if memory is running low.
>
>> Oh CRAP. I just set Xcode 4.3.1 to download the libs and documentation it doesn't have, clicked away and IT QUIT.
>>
>> WHY ARE YOU DOING THIS?
>>
>> My Mac has 11.22 GB of RAM free.
>>
>> WHY ARE YOU DOING THIS?
>
> It didn't quit; it's still downloading in the background, and it will come to the foreground once you open something in Xcode from the Finder.
This is complete and utter garbage.
In my tests, when I relaunched Xcode, the items were not downloading. I had the "Install" button all over again.
That makes no sense at all. Apple DID give us a switch to use "natural scrolling" or the method we used to use. Same with scroll bars. Apple gives us a "bounces" switch on UIScrollViews, in the source. Why not expose that when there just might be people who prefer the previous way of doing it?
All the stuff I am griping about is EXACTLY how the Mac worked over the past 25+ years, and how OS X did for 10. Apple reverses their standards on what we are used to and doesn't give us a setting to say "hey, we have new stuff, but you can still use it the way you are used to and the way we encouraged you to use it for the past decade+."
No, it's a "screw you, use it our way now, no matter what we told you for the past twenty + years".
> Nick Zitzmann
> <
http://www.chronosnet.com/>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (
email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to
email@hidden