Hi
I already posted about this problem, now maybe someone else is able to help me.
Creating ocx: http://www.winehq.com/hypermail/wine-devel/2002/09/0021.html
Catching MFC exception: http://www.winehq.com/hypermail/wine-devel/2002/09/0057.html
I now have a simple ocx and an exe that has nothing else than this ocx in it. The ocx appears as black circle on white ground in the upper left corner (right, the wizard made ocx) In Windows it works without a problem but in wine there's an exception upon creating the ocx. It happens with both builtin and native msvcrt.dll. I can see that some exceptions are raised about missing properties in the ocx, they also appear on Windows (debug output) and get caught before doing any harm. I sometimes had problems reproducing it. Then the dialog came up but without ocx.
Both exe and ocx are made with MSVC6 (Project and binaries, debug/release):
http://www.indel.ch/ftp/TestException.zip
Also here is a backtrace at the moment of the exception:
http://www.indel.ch/ftp/TestException.txt
Alexandre once asked for an example, maybe he or someone else can use this here. I'm using actual wine from cvs on SuSE8, original dlls tried from NT4.
Thanks
bye Fabi