Re: Is there a way to control where frames get created?

[martin rudalics]

> This is under MacOS/aqua:
>
> First frame:
>
> ((outer-position 0 . 23) (outer-size 675 . 874) (external-border-size
> 0 . 0) (title-bar-size 0 . 22) (menu-bar-external) (menu-bar-size 0 .
> 0) (tool-bar-external) (tool-bar-position . top) (tool-bar-size 0 .
> 0) (internal-border-width . 2))
>
> "New" frame:
>
> ((outer-position 690 . 25) (outer-size 675 . 874)
> (external-border-size 0 . 0) (title-bar-size 0 . 22)
> (menu-bar-external) (menu-bar-size 0 . 0) (tool-bar-external)
> (tool-bar-position . top) (tool-bar-size 0 . 0)
> (internal-border-width . 2))
>
> So it's two pixels different. Peculiar, eh?

As you can see, your internal border is two pixels wide.  And Alan just
noted in the thread of Bug#32882:

> I wonder if it’s the internal border. It’s not properly supported on
> the NS port for some reason, and therefore should always be the
> background colour. But it defaults to 2 pixels. Try:
>
> (set-frame-parameter nil 'internal-border-width 0)

So please try that before making the new frame.  Unfortunately, in the
follow-up Aaron said it would not change anything and I suppose you
will see the same.  But yours and Aaron's experience could eventually
lead us to where those two pixels come from.

BTW the X-position 690 of your new frame is much larger than I would
expect from 0 + 675.  So this seems even more broken.

martin