Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Office 2008 for Mac - Problem with spaces - anyone with same issue?
- Thread starter chris001
- Start date
- Sort by reaction score
Yeah after using it a little longer I found the format palette fix does not resolve the problem, though it helps (the windows behave on their own less often). I downgraded to Office 2004 and use 2008 only if I get a .docx file from a colleague.
Pages rules. If only it could open/save .doc files...
It's been able to do both for a while now (Share>Export...). The only problem is in preserving some functionality, like the ability to edit MathType equations, for example.
The Spaces/Exposé issues are a serious annoyance, and really do make using Office 2008 pretty painful.
I like Word and I really want to use spaces to separate multiple Word docs. It's almost impossible for me to place the windows where I want them. They jump from space to space constantly...like they're ***** with me. It's REALLY annoying and even more ridiculous nobody (Apple or MS) has fixed the problem.
Is this problem only for Office 2008 only? If it only happens to 2008 and not to 2004, then ill downgrade to 2004 until there is a fix for it.
It happens with Office 2004 as well. It is a well documented problem that Apple needs to fix on its end. Search the forums as members of the Microsoft Mac Business Unit have linked to a blog post that explains the conflict in great detail. The problem will eventually be resolvable once MS moves all of Office over to Cocoa or Apple figures out a work around. Until then grin & bear it.
Want an easy work around for now? Keep all Office docs in Space 1. Problem solved.
Rage!
So, would it be reasonable to conclude that if MS Office 2004 doesn't work either, then the issue has been around for 5 years? I've just switched to Mac so I dont know.. But, if that is the case, then should it not be 100% illegal to sell such faulty products? I bought the office package yesterday in complete ignorance to such an issue. The product is supposed to work with Mac, and it doesnt. And they know about it.
So, would it be reasonable to conclude that if MS Office 2004 doesn't work either, then the issue has been around for 5 years? I've just switched to Mac so I dont know.. But, if that is the case, then should it not be 100% illegal to sell such faulty products? I bought the office package yesterday in complete ignorance to such an issue. The product is supposed to work with Mac, and it doesnt. And they know about it.
Office 2004 doesn't work with Spaces (IIRC), but it's also horrible because it's not UB. Seriously, it's a nightmare- slow, clunky, and dysfunctional.
Your logic totally fails with regard to "faulty" products. What does "faulty" mean? Indeed if you search the forums for Nadyne's explanation on the matter, it seems that Apple is actually the one that has been unwilling to compromise and work with Microsoft on the issue. Go figure.
Hmmm guess so.
Still doesn't excuse either company for not sorting it. And by faulty, i mean if i spend 200 dollars (AU) on a brand new product - whatever it may be - I expect it to work. Plain and simple. If i bought a car and it unexpectedly lost a wheel out of the dealership because the company who made the wheel bolts didn't collaborate properly with the company that made the wheels, i'd want my money back!
See what I mean?
Cheers
Still doesn't excuse either company for not sorting it. And by faulty, i mean if i spend 200 dollars (AU) on a brand new product - whatever it may be - I expect it to work. Plain and simple. If i bought a car and it unexpectedly lost a wheel out of the dealership because the company who made the wheel bolts didn't collaborate properly with the company that made the wheels, i'd want my money back!
See what I mean?
Cheers
You've got a strange definition of "horrible". Yes, 2004 is PPC code, but in many cases it is faster than the 2008 UB code. I still have 2004 and have no intention of upgrading.
There was no feature called "spaces" in Mac OS X when Office 2004 came out, so of course it was never designed for the same. However, although it can have some problems with spaces, the problems are much less frequent than with the Office 2008 product.
Do you mean assign word or excel to Space 1 or just put them there manually and assign them to no space?
Yes
Open them in space 1 by default that is where they return or stay or always move to.
Do you mean assign word or excel to Space 1 or just put them there manually and assign them to no space?
Open them in space 1 by default that is where they return or stay or always move to.
so wherever they are first opened they will stay basically if you don't predefine a space and this problem goes away?
this doesn't actually fix it.. it just "helps"
but everyone should do this to cut down the amount of times it messes up.
Fixed in 10.5.7?
Seems to me there's no problem anymore after updating to 10.5.7 ! Anyone else experience the same thing?
Seems to me there's no problem anymore after updating to 10.5.7 ! Anyone else experience the same thing?
I wish! In this screen shot, you can see that word is the active program, but it's not in front
Attachments
I wish! In this screen shot, you can see that word is the active program, but it's not in front
Hmm, ok, that's a different problem, I also still have it. I was more talking about the problem that word automatically switches spaces and all that nonsense (something to do with the formatting pallete). That at least seems to work properly now.
honestly guys. I think it's too much of a hassel for microsoft to fix this problem.
it has nothing to do on apples end.
it's microsoft office which isn't compatable. so if they don't fix it. apple doesn't care.
they'll probably just come out with office 2010 and the problem will be fixed in that one...
it has nothing to do on apples end.
it's microsoft office which isn't compatable. so if they don't fix it. apple doesn't care.
they'll probably just come out with office 2010 and the problem will be fixed in that one...
I saw this post
Has 10.5.7 fix this issue?
https://forums.macrumors.com/threads/702572/
I'm not near my Mac so I can't test anything. Maybe there is good news?
Has 10.5.7 fix this issue?
https://forums.macrumors.com/threads/702572/
I'm not near my Mac so I can't test anything. Maybe there is good news?
