🚀 go-pugleaf

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.