[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Hourglass only for X-windows?

From: Eli Zaretskii
Subject: Re: Hourglass only for X-windows?
Date: Fri, 11 Mar 2005 15:28:46 +0200

> From: "Lennart Borgman" <address@hidden>
> Cc: "Eli Zaretskii" <address@hidden>, <address@hidden>,
>       "Jan D." <address@hidden>,
>       "David Hunter" <address@hidden>,
>       "Jason Rumney" <address@hidden>,
>       "KOBAYASHI Yasuhiro" <address@hidden>
> Date: Fri, 11 Mar 2005 00:33:16 +0100
> > > Personally, I think we are fine as we are now.  Of course, if you
> > > implement start_hourglass et al for Windows, the HAVE_X_WINDOWS
> > > condition needs to be augmented by something that will enable it for
> > > Windows.
> >
> > Yes, I thought I would implement start_hourglass etc.  Maybe someone wants
> > to implement it in macfns.c too where the body part also has an empty body
> > part.
> >
> > Whichever way of changing the current "#ifdef HAVE_X_WINDOWS" at those
> > places are enough, but removing the ifdef:s and adding a file with empty
> > body parts for those ports that does not implement hourglass support makes
> > the code easier to read IMO.
> I have implemented code for hourglass on w32 now (or rather I should say
> Dave Hunter has done it, I just did a small amount of typing). Could we
> please get a decision on the issue above so that it is possible to get this
> working with the CVS code? (The hourglass code in keyboard.c is currently
> only called if HAVE_X_WINDOWS is defined.)

I suggest adding WINDOWSNT to HAVE_X_WINDOWS in the condition for
calling the hourglass code.  Would that resolve the issue?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]