P
Pagemakers
When I enter a time into entourage, say 16 for the hour it enters it at 06. The only way I seem to be able to enter 16 is to use the up arrows to increase the time.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
W
William Smith
When I enter a time into entourage, say 16 for the hour it enters it at
06. The only way I seem to be able to enter 16 is to use the up arrows
to increase the time.
This is a known issue with Leopard. Not sure who's responsible for the
fix -- Apple or Microsoft?
--
bill
William M. Smith, Microsoft Interop MVP - Mac/Windows
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
D
dougst (microsoft.com)
Microsoft knows about the issue and we are working with Apple to get it
resolved.
Thanks
Doug
Doug Strauss - dougstATmicrosoftDOTcom
Microsoft - Entourage test lead
Disclaimer: This mail is provided "AS IS" with no warranties, and confers
no rights.
resolved.
Thanks
Doug
Doug Strauss - dougstATmicrosoftDOTcom
Microsoft - Entourage test lead
Disclaimer: This mail is provided "AS IS" with no warranties, and confers
no rights.
P
Pagemakers
Doug, thanks for your response but how on earth can you get such a simple thing so wrong?
J
JE McGimpsey
Doug, thanks for your response but how on earth can you get such a simple
thing so wrong?
U/I is almost never "such a simple thing"
Interfaces between hardware and applications go through many, many
layers of the operating system. When designing an application, one calls
OS routines to get and send bits.
The specification for how to do this is provided by the OS provider.
Obviously, calls to those routines worked fine with Panther and Tiger.
Something broke in Leopard. Among the possible reasons:
1) Microsoft originally implemented the wrong OS X routines, which
fortuitously happened to work in Panther and Tiger, but Leopard changed
something that made them fail.
2) Microsoft implemented the right OS X routines, and in the development
of Leopard, Apple changed the specifications for those routines and (a)
they didn't tell anyone, or (b) MS missed the change.
3) Microsoft called the right OS X routines, Apple didn't change the
specifications, but screwed up the implementation in Leopard.
4) Some combination of the above.
5) Something else entirely was introduced with Leopard.
6) Gremlins...
P
Pagemakers
Thanks guys.
Do you have a time-scale for the fix?
Do you have a time-scale for the fix?
J
JE McGimpsey
Thanks guys. <br><br>Do you have a time-scale for the fix?
Most of us are not MS employees, and those that are won't say (at least
until everything's locked down tight). Keep checking MacTopia for
announcements.
A
Andy Ruff
You might want to note that we are working with Apple on a fix for this. He
didn¹t say that we did anything wrong.
-Andy
didn¹t say that we did anything wrong.
-Andy