Re: [Mono-winforms-list] Fw: [Mono-list] System.Windows.Forms plans.

2004-07-01 Thread Peter Dennis Bartok
>You are asking for stable interfaces and those can only come once there >is a Wine 1.0. Its not here and dont get me wrong I think the Wine TODO >list is way to long and things should be close to frozen by now but >thats not the case. All you are doing is pointing out that its not >stable which i

Re: [Mono-winforms-list] Fw: [Mono-list] System.Windows.Forms plans.

2004-07-01 Thread Peter Dennis Bartok
om Wine. So, you can see it's really just a small step to then drop Wine and handle the management of Windows ourselves instead of using Wine for it. Not trying to be rude either. You asked, I answered. Peter -Original Message- From: "Steven Edwards" <[EMAIL PROTECT

Re: Wine as shared library patch

2004-03-08 Thread Peter Dennis Bartok
le codebase that doesn't intruce the potential of breaking it in the future. I may very well have overlooked something. Regards, Peter -Original Message- From: "Alexandre Julliard" <[EMAIL PROTECTED]> To: "Miguel de Icaza" <[EMAIL PROTECTED]> Cc

Re: Wine as shared library patch

2004-03-04 Thread Peter Dennis Bartok
Perhaps this could be changed to a static variable in process.c Wouldn't that make it rather hard to be set from outside process.c? I need to set it from wine-sharedlib.exe.so If you can resolve these issues then we can have a single Wine for Win32 and S.W.F! Well, you basically saw the hole hi