PDA

View Full Version : Updated to Mountain Lion




Smiley0
Apr 1, 2013, 01:16 PM
I recently updated to Mountain Lion and have noticed the following issues:

1. The SAVE AS feature being removed from Text Edit
2. Applications (like Adobe InDesign) crashing repeatedly
3. Automatic document conversion to iBooks or other "i" applications
4. Text Edit + other applications automatically saving over opened files
5. Security not allowing folder names to be changed
6. iPHOTO issues when importing from an iPHONE
7. For that matter iCLOUD is trying to do too much work for me that I don't want it to do.

BTW: I've always been a Mac user because of the operating system. I liked the fact that it didn't try to force me into a way of naming my folders.

My question is two fold: Has anyone else experienced issues like mine? And two, Has there been any talk about reverting some functionality back to SL (like the above issues)?

Thanks,
Concerned Mac User. (I might post this in the general discussion too).



Krazy Bill
Apr 1, 2013, 02:18 PM
I would suggest you do a query in the forum for each of your issues as they have been discussed repeatedly.

Has there been any talk about reverting some functionality back to SL"Talk" coming from where... here? The answer is a resounding yes - many of us would like to see that. But if you're asking whether Apple has any plans to revert 10.8 to include lost Snow Leopard features... No.

Welcome to iOS on the mac. :(

benwiggy
Apr 1, 2013, 03:05 PM
1. The SAVE AS feature being removed from Text Edit
2. Applications (like Adobe InDesign) crashing repeatedly
3. Automatic document conversion to iBooks or other "i" applications
4. Text Edit + other applications automatically saving over opened files
5. Security not allowing folder names to be changed
6. iPHOTO issues when importing from an iPHONE
7. For that matter iCLOUD is trying to do too much work for me that I don't want it to do.
1. Lion introduced MAJOR changes to the way that documents work in OS X.
2. That's something specific to your installation. InDesign (various versions) should work fine in ML.
3. What is the problem here?
4. Depending on exactly what you mean, that may relate to the change to the document metaphor.
5. That should not be any different to previous versions. This may be some problem on your machine, or you may be trying to rename a folder that you don't have permission to rename, e.g. a system folder.
6 & 7. Can you provide more details of exactly what is going on and what you want?

For a detailed assessment of ML, see this:
http://arstechnica.com/apple/2012/07/os-x-10-8/

vistadude
Apr 1, 2013, 09:46 PM
Can you re-download mountain lion and do a clean install from an external hard disk? Mountain lion should be pretty stable and should allow you to change folder names without any problem. Icloud can be disabled completely.

The automatic savings is part of the OS. It's stupid but it's what apple wants.

The first time i clean installed mountain lion, I did a transfer of data from snow leopard and it made the whole system unstable. Then I clean installed and did use os x's transfer thing and it has been rock steady stable.


I recently updated to Mountain Lion and have noticed the following issues:

1. The SAVE AS feature being removed from Text Edit
2. Applications (like Adobe InDesign) crashing repeatedly
3. Automatic document conversion to iBooks or other "i" applications
4. Text Edit + other applications automatically saving over opened files
5. Security not allowing folder names to be changed
6. iPHOTO issues when importing from an iPHONE
7. For that matter iCLOUD is trying to do too much work for me that I don't want it to do.

BTW: I've always been a Mac user because of the operating system. I liked the fact that it didn't try to force me into a way of naming my folders.

My question is two fold: Has anyone else experienced issues like mine? And two, Has there been any talk about reverting some functionality back to SL (like the above issues)?

Thanks,
Concerned Mac User. (I might post this in the general discussion too).

Krazy Bill
Apr 2, 2013, 06:16 PM
The automatic savings is part of the OS. It's stupid but it's what apple wants.

I have 3 college degrees, an engineering certificate from DeVry University and a decoder ring from Cap'n Crunch...

... I still don't understand it. :(

pionata
Apr 3, 2013, 10:50 AM
I have 3 college degrees, an engineering certificate from DeVry University and a decoder ring from Cap'n Crunch...

... I still don't understand it. :(

Dude they removed the scroll arrows and they totally messed up exposť!
Os X is fast turning into a piece of ****.

The Snow Leopard era was when Apple was at it's peak, from now on we are moving toward idiocracy and everything will just get worse until a bunch of mindless zombies eventually get their chip implanted in their brains, then it's over.

benwiggy
Apr 3, 2013, 11:55 AM
I have 3 college degrees, an engineering certificate from DeVry University and a decoder ring from Cap'n Crunch...
... I still don't understand it. :(
It's not rocket salad. :D

The whole point of computers is to automate pointless repetitive tasks. For 30 years, we've been pressing <Command> S like fury. "Don't forget to save!" Memories of losing work after a crash, because we hadn't saved, haunt us still.

Now, the computer does the saving. Documents are now ALWAYS stored on disk. Even Untitled ones. Nothing is free-floating in RAM.
In the old days, if you wanted to base one document on another, you'd just modify it and then save As. Now, you Duplicate it first as the new file, and then start modifying.
If you do decide that everything you've done today is rubbish, you can Revert to the Last Opened. Or use Versions to browse saved states, like in Time Machine.

"Remember the days when you used to have to save files by hand?":eek:

This is isn't brain-rot, it's not turning OS X into a "Toy" (People said that about the original Apple Mac, because it didn't have a CLI...!) It's just a new method of working with documents.
The old ideas from Xerox PARC are over 40 years old. Are they set in stone forever? Should we not try some new interface methods?