Hi folks,
Viktor snsed what you meant. I could not. Can you explain a little?
Sorry I was not clear enough, what I meant was that as a workaround I
changed the values of the #defines in gtwvt.h and gtxwc.c.
I misunderstood then :) and now don't get it.
As for the palette stuff, I'd use something like:
hb_gtInfo( HB_GTI_PALETTE, <nColor>[, <nNewRGB> ] ) -> <nOldRGB>
optionally:
hb_gtInfo( HB_GTI_PALETTE[, <aNewRGB> ] ) -> <aOldRGB>
where RGB could be "#ffeedd", or { nR, nG, nB }, an system
returning the former.
This way it could be stored in an .ini or wherever,
using a simple array to list conversion, in one line:
[palettes]
mypalette=#ffeedd, #ccaa99, ...
Which is of course not an ideal situation.
In general I think Harbour should extend the "colors syntax" since in
this way strings like "B/W+" have no meaning.
It would be nice if colors could be set using sth like
"#ff55ff/#cb3f56" or "{255,123,255}/{178,83,156}"
Instead numbers strings like "1/13" are useful as reference to the
palette's colors.
Numbers can be used in Harbour, just like in Clipper.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
