From: Shawn Jefferson (sjefferson_at_sd62.bc.ca)
Date: 2002-10-31 23:10:57
>>> Ullrich von Bassewitz <uz_at_musoftware.de> 10/31/02 12:36PM >>> > >On Thu, Oct 31, 2002 at 12:29:54PM -0800, Shawn Jefferson wrote: >> I'm thinking that it has something to do with the fact that I am using >both >> conio functions and printf. Perhaps they maintain a different set of >> coordinates or something else weird is going on? > >I can only comment on this one: You should not use both, conio and standard >C >file I/O to write to the screen. This is true not only for the Atari but >for >almost all other platforms. You may get weird effects when doing so. The >reason is - as you suspected - that the conio subsystem may use its own >variables for cursor position, size, state or whatever. Ok. That certainly seems to be what is going on. I just wrote a little test program and verified that the conio function cursor() doesn't turn the cursor on/off on the atari. That leaves me in a sticky situation, since I want the cursor to appear during my text_input function, but not during the rest of the screen drawing. Further this is complicated by the fact that you have to do an output through the E: handler after toggling the cursor on the Atari, which conio doesn't do. I'd like to keep using the conio functions for speed though. I guess the quick solution is for me to just move the E: device cursor coordinates myself before doing my printf in text_input. I was using gotoxy() thinking that this is what it did... Thanks for your help! -- Shawn ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo_at_musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2002-10-31 23:11:45 CET