X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: "Giorgio Medeot" Newsgroups: comp.os.msdos.djgpp References: Subject: Re: strange bright/blink behavior Lines: 34 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-ID: Date: Sun, 28 Sep 2003 12:37:37 GMT NNTP-Posting-Host: 151.25.147.221 X-Complaints-To: abuse AT libero DOT it X-Trace: twister1.libero.it 1064752657 151.25.147.221 (Sun, 28 Sep 2003 14:37:37 MET DST) NNTP-Posting-Date: Sun, 28 Sep 2003 14:37:37 MET DST Organization: [Infostrada] To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com > Giorgio Medeot wrote: > > > When I launch foo.exe, if the DOS prompt is located at the bottom of the > > screen, so that executing foo.exe causes the screen to scroll, all new > > lines that are printed also look as they had the blink bit set. > > I suspect that's because the effect of updating "ScreenAttrib" only takes > place if you actually output a character. If I putch() a new character after restoring ScreenAttrib, it looks ok (so "ScreenAttrib" should have been updated); but after foo has exited, new lines on the screen still blink. Moreover, if I type at the DOS prompt: cls foo.exe nothing strange happens, but if I press the enter key many times, reaching the bottom of the screen, and then I type foo.exe, pressing now enter gives me the blinking lines. This makes no sense to me. > I think you should rather use one of the other functions > instead of putch(), which take the attribute as one of their > arguments, and leave ScreenAttrib alone. See, e.g., ScreenPutChar(). I'll give it a try, but it's a little tedious to me having to get the current cursor position every time I need to print a character Thank you for helping, Jo.