Just tested it, and visual glitches are now all gone in
GTWVT UNICODE mode. Thank you very much.
Fine.
I would like to ask about keeping some builds in UNICODE mode
so thay can be tested in the future. AFAIR UNICODE mode was fully
functional about two years ago and we lost it by some modifications
which were not well tested.
I've recently enabled UNICODE for all non-x86 win builds
exactly for above reason.
I'll also enable it for MSVC 2008, as this compiler doesn't
support Win9x anyway. This will need a little more work for
generic compiler version setting.
What remains is the char encoding problem. It seems as
if in UNICODE mode the HB_GTI_CODEPAGE setting is ignored.
Yes it is and it's intentional.
HB_GTI_CODEPAGE is MS-Windows only extension used in non UNICODE
mode.
Use hb_setTermpCP()/hb_setKeyCP()/hb_setDispCP() just like in
all other GTs. See tests/gtchars.prg
Oh I see. I was missing hb_setTermCP() in Windows builds.
Adding it fixed GTWVT UNICODE build. (I didn't retest non-UNICODE
yet, I hope it stays OK too)
Plus, after your latest GTWIN fix, the CP is working good
here also. Very nice, thanks!
With GTWIN the remaining problems are HB_GTI_WINTITLE
CP in UNICODE mode (I didn't report this before), plus the
high level drawing (seemingly window related) problem. I'll
try to make tests with 32-bit UNICODE to check what exactly
enables this.
[ Something similar happens in UNICODE GTWIN, but there I'm
seeing '?' chars. ]
GTWIN was never updated to work internally in UNICODE mode so
I guess it has problem with non ASCII characters. It should be
quite easy to add support for UNICODE mode for someone who
can verify the results on the screen.
Hm, I can verify it. But modifying it was beyond my knowledge,
last time I changed this part. Update: Your fix verified OK.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
