* Changed color representation to be 'int' in all places.
This means changes in high level and low level GT interfaces.
; QUESTION: In hbct UCHAR is used in a few places, I didn't want
to
touch it.
But you already touched it indirectly :-)
In the moment when you changed BYTE to int as color holder this code:
const char * szAttr;
...
hb_gtPutChar( iRow, i++, szAttr[ ul ], 0, ( UCHAR ) *szText++ );
begins to give wrong results. Now you have to add explicit casting
hb_gtPutChar( iRow, i++, ( UCHAR ) szAttr[ ul ], 0, ( UCHAR )
*szText++ );
otherwise you will have problems with neagtive values.
We have to locate all places which can be affected by above
modifications
and add such casting.
I'll commit in a while some additional modifications: we still
cannot pass
unicode (U16) character in few places because BYTE is used.
Thanks for the co-op.
Some more things I'd like to do:
BYTE/USHORT as drive in API FS to be changed to int.
What should be a final all-round type for single chars? int or USHORT?
or hbU16?
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
