wine users - May 2010 - Wineboot: useless dialog

Hi!

I wonder about something, which disturb me:
thisone (wineboot.c):

Code:
static INT_PTR CALLBACK wait_dlgproc( HWND hwnd, UINT msg, WPARAM wp, LPARAM lp
)
{
    switch (msg)
    {
    case WM_INITDIALOG:
        {
            WCHAR *buffer, text[1024];
            const WCHAR *name = (WCHAR *)lp;
            HICON icon = LoadImageW( 0, (LPCWSTR)IDI_WINLOGO, IMAGE_ICON, 48,
48, LR_SHARED );
            SendDlgItemMessageW( hwnd, IDC_WAITICON, STM_SETICON, (WPARAM)icon,
0 );
            SendDlgItemMessageW( hwnd, IDC_WAITTEXT, WM_GETTEXT, 1024,
(LPARAM)text );
            buffer = HeapAlloc( GetProcessHeap(), 0, (strlenW(text) +
strlenW(name) + 1) * sizeof(WCHAR) );
            sprintfW( buffer, text, name );
            SendDlgItemMessageW( hwnd, IDC_WAITTEXT, WM_SETTEXT, 0,
(LPARAM)buffer );
            HeapFree( GetProcessHeap(), 0, buffer );
        }
        break;
    }
    return 0;
}




Why is this there?
I'm still dedicated to the UNIX philosophy: If there is no error, be quit.
I didn't like that wine is getting more and more this verbiage used in
windows.
A car brake wrote:
> You just push the brake. You really want to slowdown your speed? Press OK
or Cancel
Please, please, let this things away. Do wine in a chaste and simple way.
Thanks a lot!

sotel wrote:
> Hi!
>
> I wonder about something, which disturb me:
> thisone (wineboot.c):
>
> Code:
> static INT_PTR CALLBACK wait_dlgproc( HWND hwnd, UINT msg, WPARAM wp,
LPARAM lp )
> {
>     switch (msg)
>     {
>     case WM_INITDIALOG:
>
>
>
>
> Why is this there?
>   
Maybe because some Windows programs expect it to be there? 
> I'm still dedicated to the UNIX philosophy: If there is no error, be
quit.
> I didn't like that wine is getting more and more this verbiage used in
windows.
>   
You must not understand, oh young one, that Wine is a COMPLETE 
implementation of the Windows 32 (and now Windows 64) API, bugs and 
problems.  We cannot and will not 'choose and pick' what functionality 
that will or will not be built into this project.  Microsoft already did 
this for us.
> A car brake wrote:
>   
>> You just push the brake. You really want to slowdown your speed? Press
OK or Cancel
>>     
>
>   
If that happens, I'll crash the car.
> Please, please, let this things away. Do wine in a chaste and simple way.
>   
No.  Please read my comment above.  Wine IS NOT LINUX/UNIX.  Wine IS THE 
WINDOWS API.  They are and will not be the same.

James McKenzie

James McKenzie wrote:
> sotel wrote:
> 
> > Hi!
> > 
> > I wonder about something, which disturb me:
> > thisone (wineboot.c):
> > 
> > Code:
> > static INT_PTR CALLBACK wait_dlgproc( HWND hwnd, UINT msg, WPARAM wp,
LPARAM lp )
> > {
> > switch (msg)
> > {
> > case WM_INITDIALOG:
> > 
> > 
> > 
> > 
> > Why is this there?
> > 
> > 
> Maybe because some Windows programs expect it to be there? 
> 
> 
> > I'm still dedicated to the UNIX philosophy: If there is no error,
be quit.
> > I didn't like that wine is getting more and more this verbiage
used in windows.
> > 
> > 
> You must not understand, oh young one, that Wine is a COMPLETE 
> implementation of the Windows 32 (and now Windows 64) API, bugs and 
> problems.  We cannot and will not 'choose and pick' what
functionality
> that will or will not be built into this project.  Microsoft already did 
> this for us.
> 
> > A car brake wrote:
> > 
> > 
> > > You just push the brake. You really want to slowdown your speed?
Press OK or Cancel
> > > 
> > > 
> > 
> > 
> > 
> If that happens, I'll crash the car.
> 
> 
> > Please, please, let this things away. Do wine in a chaste and simple
way.
> > 
> > 
> 
> No.  Please read my comment above.  Wine IS NOT LINUX/UNIX.  Wine IS THE 
> WINDOWS API.  They are and will not be the same.
> 
> James McKenzie

Personally I agree with the original poster, it's an annoying dialog.  If
nothing is wrong why do I need to see it?

James, it makes no sense for a windows program to expect a dialog from wineboot.
It has nothing to do with compatibility.  I would wager it's there so that
users understand something is happening in the background.