home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: alt.lang.basic
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!jvnc.net!phage!boutell
- From: boutell@isis.cshl.org (Tom Boutell)
- Subject: Re: Calling QuickC from QuickBasic
- Message-ID: <Bxz8Kx.BF8@phage.cshl.org>
- Sender: news@phage.cshl.org
- Organization: Cold Spring Harbor Labs
- References: <922112112145@ibm3090.bham.ac.uk>
- Date: Thu, 19 Nov 1992 18:55:45 GMT
- Lines: 28
-
- My mailer didn't know you. Here we go again:
-
-
- Interesting situation. Your problem is making sure that C and Quickbasic
- both "know" what mode you're in so they'll execute the right code for
- the mode. A cheap nasty solution:
-
- At the beginning, when you set the graphics mode, do it in both:
-
- SCREEN N (in Quickbasic; clears the screen and sets graphics mode
- so your code will know about it)
- call croutine()
-
-
- void croutine() {
- _setupvideo(...same mode for Quick C...);
- }
-
- So the screen gets cleared twice, which is a waste but not noticeable if it
- only happens when the program first starts up, and now both libraries
- think they're in the same mode.
-
- -T
-
- --
- Tom Boutell, boutell@cshl.org
-
- Clausthaler is the best non - alcoholic beer in the known universe.
-