Office and Spaces

[CyberTaz]

And once again ... Nobody here has an answer to that question. The
participants in this group are *users* of the product & have no control or
insight on "ifs" or "whens" regarding revisions/fixes to any developer's
software. Those who "may" know don't hang out here & aren't at liberty to
disclose any knowledge they may have in the first place.

Regards |:>)
Bob Jones
[MVP] Office:Mac

 

[mattbacon]

Well... this is certainly an issue I'm familiar with, but (on my Air with 10.5 up to date) the workaround is usually just to press the button to close the floating formatting palette and then click again to re-open it. At which point it reappears next to the correct application. In my experience, the phenomenon usually occurs when the formatting palette is tiled directly adjacent to the working window (and hence hits the screen edge in the space). Usually when it's reopened it floats slightly over the working window, doesn't hit the edge of the screen, and works normally. It's a pain, but not so much that I feel the need to revert to 2004 or turn off Spaces, which I use a LOT...

bestest,
M.

 

[Rainer]

:

It's kinda like having purchased a piece of equipment (OS X Tiger) and
buying an accessory designed for it (Office 2008) then turning around &
replacing the equipment with a new, redesigned model (OS X Leopard)... The
accessories designed for the previous model "may" or "may not" still work in
all respects as they did with the model for which they were designed

I cannot agree with your statement. MacOSX 10.5 has been around for over a
year now, Office 2008 also had a number of updates. Following your reasoning
then the only correct thing for M$ to do is to state that Office 2008 is NOT
COMPATIBLE with MacOSX 10.5!!! There are so many bugs with spaces that
basically every app apart from Entourage is completely unusable. You cannot
expect users to change their whole working style only because one company
cannot get their head around adapting to the changed environment. Until this
has been achieved, they need to put a sticker on stating that it WILL NOT
WORK with 10.5.

comprehend - rarely can you just change a "$" to a "%" somewhere within
millions of lines of code in order to "fix" something - at least not without
the very real potential to "break" a number of other things.

There are a number of tools that professional software developers should
employ to make them still be able to change certain things without running
the risk of breaking the whole program (unit test, automation tests,
integration tests, ...). So while I completely understand that it might not
be trivial to fix this problem, they need to step up and state that you
simply should not use it until it does and offer a money back (I wonder
however, why 98% of all Mac software plays nice with spaces and only a few do
not, that makes me wonder who is at fault).