nanogui: Is there a #define constant for MicroWindow ???
Subject:
Re: [nanogui] Is there a #define constant for MicroWindow ???
From:
Jordan Crouse ####@####.####
Date:
8 Nov 2001 18:42:50 -0000
Message-Id: <E161u8V-0000lq-00@ns.censoft.com>
That sounds like a good idea, but what if its not? Communication would be
almost impossible anyway, so its not like you could just adapt on the fly.
Jordan
On Thursday 08 November 2001 11:38, Gary James mentioned:
> Hey Guys,
>
> Providing a couple pound defines doesn't mean that you will
> automatically start writing conditionally compiled code. On the other
> hand, not providing pound defines prevents other people from writing
> conditionally compiled code. It would be nice to make every body
> happy (peace, love, and all ya know baby ;).
>
> On a slightly different but related topic...
> (I apologize if this is already in place)
>
> It might be nice to be able to determine from within a nano-X client
> if the nano-X server is the same revision.
>
> Gary James
>
>
>
>
> From: Jordan Crouse ####@####.####
> Send reply to: ####@####.####
> Organization: The Microwindows Project
> To: "Greg Haerr" ####@####.####
> ####@####.####
> ####@####.####
> Date sent: Thu, 8 Nov 2001 10:42:02 -0700
> Subject: Re: [nanogui] Is there a #define constant for MicroWindow
> ???
>
> > Its not so much *having* to have a define, but rather, *providing* a
> > define so that the code can be more intellegent.
> >
> > For example:
> >
> > You might use the following block of code to compile for both pre6 and
> > pre8:
> >
> > #ifdef __MW89PRE8__
> > GrSetScreensaverTimeout(1000);
> > #endif
> >
> > See... The define provides a way to compile for mutiple versions, even
> > with a changing API (especially since our API changes almost hourly
> > these days... :) )
> >
> > Jordan
> >
> > On Thursday 08 November 2001 10:27, Greg Haerr mentioned:
> > > : This might not be a bad idea to stick a #define __MICROWIN__
> > >
> > > somewhere. : Even better would be #define __MW89PRE8__ (for each
> > > version) to write : more portable code.
> > >
> > > I am not in favor of this. I much prefer the _GNUC_ or _MSCVER_
> > > that Gary James suggests. I hate _having_ to have a define in order
> > > to compile code.
> > >
> > > Regards,
> > >
> > > Greg
> > >
> > > : Jordan
> > > :
> > > : On Thursday 08 November 2001 09:20, Greg Haerr mentioned:
> > > : > : I search a #define value wich identify when i compile for : >
> > > : >
> > > : > MicroWindow. : > Is there one wich identify a true win32
> > >
> > > environnement ? : > : > Not really. You might use MWINCLUDECOLORS :
> > > > possibly which is used in src/include/mwtypes.h : > to include
> > >
> > > Microwindows color definitions. : > : > Otherwise, Microwindows
> > > itself doesn't need any define. : > Windows used to use _WIN32 and
> > > _WINDOWS : > I think. Perhaps you could use that. : > : > Regards,
> > >
> > > : > : > Greg : > : > : >
> > >
> > > --------------------------------------------------------------------
> > >
> > > - : > To unsubscribe, e-mail: ####@####.#### :
> > > > For additional commands, e-mail: ####@####.####
> > >
> > > --------------------------------------------------------------------
> > > - To unsubscribe, e-mail: ####@####.#### For
> > > additional commands, e-mail: ####@####.####
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: ####@####.#### For
> > additional commands, e-mail: ####@####.####
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
