gerard patel writes:
> At 10:53 PM 10/22/00 +0200, you wrote:
> 
> >I don't think this is a fix. It only hides the real problem:
> >Some builtin-commdlg function failed without setting 
> >COMDLG32_SetCommDlgExtendedError. The application sees the failed
> >function and wants to know the reason.
> >
> >So the failing function is better fixed and the check left in to see
> >where and when those problems appear.
> >
> 
> Seems pure wisdom to me.
> I just tried to add a COMDLG32_SetExtendedError(0) to
> Filedlg_Init (it seems logical to initialize the error code no...)
> and it removes the messages for Notepad 16 bits as well.
> 

Well, is the situation "pressing ESC in the file open dialog"
indicated by WinXX with COMDLG32_SetExtendedError(0) or does it have
some special error?

Bye

Uwe Bonnes                [EMAIL PROTECTED]

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------



Reply via email to