Hi res,

Wednesday, August 29, 2007, 3:46:52 PM, you wrote:

> On 29.08.2007 15:24, Piotr Obrzut wrote:
>> ok, then try to build the plugin with wxWidgets in Unicode, without
>> UNICODE. Check this:
>> 
>> 1>------ Build started: Project: appwxtest, Configuration: Debug Win32 ------
>> 1>Compiling...
>> 1>wxtest.cpp
>> 1>e:\programowanie\wxwidgets-2.8.4\include\wx\msw\winundef.h(39) : error 
>> C2664: 'CreateDialogParamW' : cannot convert parameter 2 from 'LPCTSTR' to 
>> 'LPCWSTR'
>> 1>        Types pointed to are unrelated; conversion requires 
>> reinterpret_cast, C-style cast or function-style cast

> Hmm. The Win32 headers use UNICODE to "switch" functions, but that
> header uses "_UNICODE", apparently assuming that when one is set, the
> other is as well. But I don't know whether this has a good reason and is
> intentional or whether it's an oversight by the WX developers...

> But OTOH, it seems there's wxUSE_UNICODE to control whether WX is built
> w/ UNICODE ... all slightly confusing.

> -f.r.

my impression was that you need to use UNICODE on your side and you
need to build wxWidgets with wxUSE_UNICODE (which is exactly what
you've said).

Either way - currently it looks working, could you please add this
change to 1.2?

-- 
greetings,
 Piotr Obrzut                           mailto:[EMAIL PROTECTED]


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Crystal-main mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/crystal-main
Unsubscribe: mailto:[EMAIL PROTECTED]

Reply via email to