ActiveX COM - Unicode vs Non-Unicode

Print Page | Close Window

Unicode vs Non-Unicode

Printed From: Codejock Forums
Category: Codejock Products
Forum Name: ActiveX COM
Forum Description: Topics related to Codejock ActiveX COM products
URL: http://forum.codejock.com/forum_posts.asp?TID=11218
Printed Date: 21 November 2024 at 11:54am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: Unicode vs Non-Unicode

Posted By: griswald88
Subject: Unicode vs Non-Unicode
Date Posted: 26 June 2008 at 1:16pm

I understand that the unicode versions of the com components support foreign characters, but I wanted to know other than characterset implementation, is there any other differences between the two versions, particularly with the CommandBars and TaskPanel? We localize our applications and would prefer to use the unicode controls, but we have implemented everything so far using the ANSI controls. What impact would switching to the unicode controls have, if any?

Replies:

Posted By: Oleg
Date Posted: 27 June 2008 at 1:27am

Hi,

Don't think you will notice any difference instead of charset support.

Main difference that Unicode version don't work with win9x.

-------------
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS

Posted By: nighthawk
Date Posted: 27 June 2008 at 4:24pm

I don't know how unicode works from a technical level but is it possible for you to combine the unicode and non-unicode versions. Either make it auto-detect whether or not unicode is supported or else have a setting which will turn it on and off? Right now I'm using the non-unicode version because I need to support Win9x but I also would like to also support other languages for those who have a newer OS.

Posted By: Baldur
Date Posted: 11 July 2008 at 10:25am

Normaly it's no problem, if you use the ActiveX-Versions.

The CLSID's and Typelib-Id from both versions are the same.

If you run the CJ COM-Registrator you can switch between this versions without any effect.

So for Win9X you can deliver the non-unicode and for other you can deliver the unicode-versions.

Your Application can ask the Unicode-Property of CJ's control.

Because COM-interfaces use BSTR for Strings, this are always Unicode (for windows also named WideChar).

Only the UI's of windows himself doesn't support WideChar in 9X.

Posted By: nighthawk
Date Posted: 11 July 2008 at 11:15pm

I'll have to test out using both unicode and non-unicode versions of the ocxs. I'm not going to create a seperate installation package for both versions so I will have to bundle them together, which will increase the size of my installation program by several MB. Not ideal but if it works smoothly, I may still go with that option.