RE: [Plib-devel] Re: [PATCH] puListBox: don't use hard-coded colo rs

[Fay J. F C. AAC/W. <joh...@eg...>]

Why would it break backward compatibility for the input box?  We could
initialize it to whatever the present color is and not change it unless the
application changes it.   Applications that don't know about would not
worry.

John F. Fay
Technical Fellow, Jacobs/Sverdrup TEAS Group
850-729-6330
joh...@eg...
 
-----Original Message-----
From: pli...@li...
[mailto:pli...@li...] On Behalf Of Melchior FRANZ
Sent: Thursday, September 15, 2005 1:58 PM
To: pli...@li...
Subject: Re: [Plib-devel] Re: [PATCH] puListBox: don't use hard-coded colo
rs

On Thu, Sep 15, 2005 at 11:56:36AM -0500, Fay John F Contr AAC/WMG wrote:
> The "PUCOL_MAX" is used for an array
> dimension and as such is not available to be a separate color.

lol ... I know, of course. I just mentioned it because it shows that the
system is prepared to have further colors added.  :-)
 
 
 
> We could presumably increase it from six to seven and add a new PUCOL 
> constant ("PUCOL_INPUTAREA"?)
 
That's what I had in mind as the clean solution, but wasn't sure if it would
be OK, because ...
 
 
 
> without breaking any backward compatibility.
 
Not if you use this only for the combo and the select box.
But, to be consistent, you'd also have to use it for the input box. And then
it /does/ break compatibility. Hence my concerns.
Or could we add the new color constant as /additional/ input field color for
the input object (and possibly depreciate the old one after a while)?
 
m.


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
plib-devel mailing list
pli...@li...
https://lists.sourceforge.net/lists/listinfo/plib-devel