Thank you for your post. We have been in development of adding unicode support to LabWindows/CVI for a little while now. As it is a large feature, users should see unicode support added in the next couple of years.
Regards,
Collin Draughon
LabWindows/CVI Product Manager
National Instruments
support of Unicode character set would be most welcome
I second this wish. And actually it shouldn't be that difficult, it could even be handled more conveniently than Windows itself does it: Win9x compatibility is of no concern anymore anyway, so a switch from the -A to the -W APIs poses no problem. Now, instead of redesigning the whole CVI API to accept wide characters, stick a MultiByteToWideChar call before every UI/Text API call and convert the string according to the character set of the meta font. This is what Windows does internally for the -A APIs anyway and this way old CVI code remains 100% compatible. The only twist is that you can now allow UTF-8 as another "character set", which MultiByteToWideChar already knows how to handle, and voila, complete Unicode compatibility.
No compiler change (for wide strings), no API change, just a few adjustments to the runtime library... I mean yeah, there might be a few more details to worry about, but the important thing is that Unicode support doesn't need to be UTF-16. In my opinion UTF-8 is more convenient anyway!
Thank you for your post. We have been in development of adding unicode support to LabWindows/CVI for a little while now. As it is a large feature, users should see unicode support added in the next couple of years.
I am very glad that the Idea Exchange seems to be alive again after being apparently dead for almost three years...
However, your comment that - five years after the suggestion - implementation will take place in the next couple of years, sounds, hm, how should I say, not exactly ambitious
But who knows, maybe CVI 2017 will provide some other "large" feature to make us excited again
If (when??) you do this, please also include updating the SQL Toolkit so that we can select from and insert data into NVARCHAR columns in true unicode (e.g. add the appropriate "DBBindColNChar" etc functions).
Hi Wolfgang,
Thank you for your post. We have been in development of adding unicode support to LabWindows/CVI for a little while now. As it is a large feature, users should see unicode support added in the next couple of years.
Regards,
Collin Draughon
LabWindows/CVI Product Manager
National Instruments