Bug in time input

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.

William
Wed Jan 16 22:43:52 CST 2008

Pagemakers@officeformac.com wrote:
> 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/>

dougst
Thu Jan 17 15:42:45 CST 2008

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.

On 1/16/08 8:43 PM, in article eqmZQOMWIHA.5816@TK2MSFTNGP06.phx.gbl,
"William Smith" <mecklists@REM0VETH1S.comcast.net> wrote:

> Pagemakers@officeformac.com wrote:
>> 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?

Pagemakers
Thu Jan 17 17:10:48 CST 2008

Doug, thanks for your response but how on earth can you get such a simple thing so wrong?

JE
Fri Jan 18 11:18:12 CST 2008

In article <ee88e58.1@webcrossing.caR9absDaxw>,
Pagemakers@officeformac.com wrote:

> 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...

Pagemakers
Fri Jan 18 12:35:20 CST 2008

Thanks guys. Do you have a time-scale for the fix?

JE
Sat Jan 19 06:50:12 CST 2008

In article <ee88e58.4@webcrossing.caR9absDaxw>,
Pagemakers@officeformac.com wrote:

> Thanks guys. 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.

Andy
Sat Jan 19 09:15:14 CST 2008

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3283571715_116188
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: 8bit

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

On 1/17/08 3:10 PM, in article ee88e58.1@webcrossing.caR9absDaxw,
"Pagemakers@officeformac.com" <Pagemakers@officeformac.com> wrote:

> Doug, thanks for your response but how on earth can you get such a simple
> thing so wrong?

--B_3283571715_116188
Content-type: text/html;
charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: Bug in time input</TITLE>
</HEAD>
<BODY>
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 
 
 
On 1/17/08 3:10 PM, in article ee88e58.1@webcrossing.caR9absDaxw, "Pag=
emakers@officeformac.com" <Pagemakers@officeformac.com> wrote:<BR=
>
 
<BLOCKQUOTE>Doug, thanks for your resp=
onse but how on earth can you get such a simple thing so wrong? 
</BLOCKQUOTE>
</BODY>
</HTML>

--B_3283571715_116188--

Bug in time input

Re: Bug in time input by William

Re: Bug in time input by dougst

Re: Bug in time input by Pagemakers

Re: Bug in time input by JE

Re: Bug in time input by Pagemakers

Re: Bug in time input by JE

Re: Bug in time input by Andy