C1 Community
ComponentOne Community is a free source for developers and help authors to collaborate and communicate.

Unicode Header problem.

rated by 0 users
This post has 4 Replies | 2 Followers

Not Ranked
Posts 1
Hi there.
I'm using VSFlexGrid8 (UNICODE) 8.0.20044.210.
and there is a bug obviously not happening on the None-Unicode version.

After setting a header of its, i mean 'formatstring',
some characters are disappeared.
Chinese and Korean, both of them. 名, 순서, 관, etc.

check out an example.

thanks in advance.


Top 25 Contributor
Posts 665
Hi,
 
I tested this with the latest OCX files. I am attaching the snapshot. Could please tell me if you see something wrong and point me into that direction.
 
Regards,
Dave
<heesung> wrote in message news:197079@10.0.1.98...
Hi there.
I'm using VSFlexGrid8 (UNICODE) 8.0.20044.210.
and there is a bug obviously not happening on the None-Unicode version.

After setting a header of its, i mean 'formatstring',
some characters are disappeared.
Chinese and Korean, both of them. 名, 순서, 관, etc.

check out an example.

thanks in advance.




http://helpcentral.componentone.com/cs/forums/p/72595/197079.aspx#197079

Not Ranked
Posts 2
Lesoch replied on Sat, Jan 05 2008 7:21 AM

I came across the same problem recently. Certain unicode characters do not appear in the column header if I used a FormatString like    

    fg.FormatString =  "|" & ChrW$(&H59D3) & ChrW$(&H540D)

In this case, the first unicode appeared correctly but the second one  didn't show. BTW, the second code is the first unicode in the example given by heesung. I am using the most recent version (2007.3) of VSFlexGrid8.

However, if I used for example

  fg.TextMatrix(1, 2) = ChrW$(&H59D3) & ChrW$(&H540D)

for the header column, it appeared fine.

Your snapshot looked right. Can you give us the code sniplet that you used? I feel it is a bug (hopefully not a feature) in  VSFlexGrid8.

 

Top 50 Contributor
Posts 111
Shragel replied on Sun, Jan 06 2008 6:37 PM

The format property removes the unicode.

Not Ranked
Posts 2
Lesoch replied on Sat, Jan 12 2008 4:05 PM

But it showed the first Unicode correctly, only the second one and after didn't.

Page 1 of 1 (5 items) | RSS
Contact ComponentOne: 1.800.858.2739 ©1987-2009 ComponentOne LLC All Rights Reserved.