Steema Central

Hi,

I'm testing an Eval version of TeeChart2010 in C++ MFC UNICODE application.

1)I have a simple window with TeeChart control and I can call TeeEditor.
2)There, I go and change graph title by typing or pasting unicode (any non-Roman - Chinese, Japanese, Arabic or Cyrillic) text. It shows up in the title of the graph fine.
3)Then, I get this text string from the graph programmaticaly (ipHeader->get_Caption(&bstring))

I can see in the debugger only ?????????. If I put this string back to the graph header those question-marks will show up in the graph.
I would like to be able to get strings from graph and put them back. Any idea?

Thanks,
Alex.

Hello Alex,

Could you try to arrange a simple example project we can run as-is to reproduce the problem here. So can try to find a good solution for you.

Thanks,

Please, see uploaded project: testUnicodeTee2010Eval.zip

Hello ESRI

Seems that your project don't attach your project testUnicodeTee2010Eval.zip, please could you attach again your project.

Thanks,

It's uploaded to your server via http://www.steema.net/upload/
Can you see it?

Hello ESRI,

I have found the file, thank you. We have made any test with your project. We'll answer you asap.

Thanks,

Hello ESRI,

Please, could you check if you do the reverse as you doing now, using Set_Caption with Unicode characters-"负载转矩"- when initialize chart, also appears this -????- ?

Thanks,

put_Caption works fine:

ITitlesPtr ipTitles(m_chart.get_Header());
ipTitles->put_Caption(_bstr_t(L"负载转矩"));

after calling lines above, I can see the "负载转矩" string in the title of a chart window. But if I call get_Caption right after:

BSTR bstrCaption;
ipTitles->get_Caption(&bstrCaption);

I see "?????" in Debugger for bstrCaption. Calling put_Caption immediately after will turn title on the chart to "??????"

ipTitles->put_Caption(&bstrCaption);

So, my guess would be that get_Caption somehow ruins UNICODE.

Hello ESRI,

We've reproduced it and we've found the problem in TeeChart ActiveX v2010. We've just corrected it so it will be fixed with the next maintenance release.
If you need it, we can prepare an ocx updated for you.