This would lead to a more complex macro/function, but would, I think be worth it.
[snip]
It would be a more complicated macro/function - but I agree with you, it would be worth it.
This works nicely for the ANSI versions of the call, which return th ANSI encoded string of bytes that is suitable for directly inserting into the PV, but this doesn't address the Unicode issue at all, where the string copied by CB_GETLBTEXT would have to be converted from UCS-2 to utf-8 and then copied into the SV, setting the SVf_utf8 flag appropriately.
If we spend time on reworking some of the internals for Unicode is it worth us considering the implications of 64bit further down the road?
Cheers, jez.
