Re: [cc65] wrong colors in conio

Date view Thread view Subject view

From: Christian Groessler (cpg_at_aladdin.de)
Date: 2002-12-11 01:06:41


Hi,

On 12/11/2002 12:32:57 AM CET Ullrich von Bassewitz wrote:
>
>On Tue, Dec 10, 2002 at 05:50:32PM +0100, Christian Groessler wrote:
>> But then I cannot follow the argument that textcolor() should do
>> nothing instead of setting the luminance as it is now.
>> If textcolor does nothing, your simplemenu silently will not work
>> correctly anyway since the text brightness is undefined.
>
>If you need some other sample code, have a look at the debugger module that
>comes with cc65. It has several calls to textcolor() and works on both,
>monochrome and color machines. Without a textcolor function that does nothing,
>it would need additional defines, either #ifdef'ing each call to textcolor(),
>or better, defining a dummy textcolor function that does nothing. But if I
>need a dummy textcolor function to make the code portable, why cannot conio
>supply such a function?

A null textcolor will only work _sometimes_, i.e. depending on the
choice of background color.
So you will anyway need ifdefs to correctly support the Atari. You
might not notice this if calling textcolor work, if textcolor is
missing, you'll notice immediately.

The reason I'm bitching so much, is that I still don't see the
benefit of having an empty textcolor() and a new textluminance() over
having a textcolor() which behaves differently on the Atari.

regards,
chris

----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo_at_musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.


Date view Thread view Subject view

This archive was generated by hypermail 2.1.3 : 2002-12-11 01:08:04 CET