On Thu, 08 Oct 2009, Szak�ts Viktor wrote: Hi,
> hb_setTermCP() will mess up the keyboard input for national > chars when used in UNICODE builds, while it won't for non-UNICODE > builds. Tested with GTWVT. > The point here is not the "mess up" part, but rather that > app behavior is different in UNICODE and non-UNICODE builds. > This is most probably not right this way. (the culprit is > hb_setKeyCP() behavior) I do not understand what is the problem in your case but for sure above does not discribe GTWVT behvior. For both UNICODE and non UNICODE modes all you should use: hb_setTermCP( <cTermCP>, <cHostCP> ) where <cTermCP> is OS encoding and <cHostCP> is HVM encoding. When <cHostCP> is not given then _SET_CODEPAGE is used. The only one difference between UNICODE and non UNICODE mode is the fact that in UNICODE mode <cTermCP> is ignored and only <cHostCP> is significant but for user code it does not create any differences. best regards, Przemek _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
