Subject: Re: bug#37415: Asserting failure setting frame parameters to non-fixnum values in early-init.el

From: Eli Zaretskii <[email-masked]>
Date: Tue, 24 Sep 2019 10:41:58 +0300

> Cc: [email-masked], [email-masked]
> From: martin rudalics <[email-masked]>
> Date: Tue, 24 Sep 2019 08:45:43 +0200
> 
>  >> What bothers me more is that we base the Windows code on a concept
>  >> that it can neither understand nor control.
>  >
>  > Which concept is that?
> 
> Size hints.  In particular the 'user-position' frame parameter.

Well, that has been working for far too long to be bothered now, I
think.

>  > The 'else' block is redundant, because when the hint flags are set,
>  > w32_createwindow will disregard coords[].  But it does no harm, so if
>  > you are more comfortable with it, fine.
> 
> Thanks but don't bother.  Better leave a short note in a comment
> explaining how this is supposed to behave.

Done.

> On a related note: Do you have any ideas what the window_prompting
> argument of w32_window is or was for?

It's unused, and was unused since the initial revision of that
function.  I think it's there just to keep the signature compatible
with that of x_window (which itself only keeps that compatibility in
toolkit versions).