Re: x-display-pixel-width/height inconsistency

[Jan Djärv]

5 jul 2013 kl. 00:32 skrev Juanma Barranquero <address@hidden>:

>> On Windows frame and client rectangle include the toolbar.  So I'm not
>> sure how to generalize this conveniently.
> 
> Oh.
> 
> Anyway, backtracking a bit in this thread... We were talking about
> multi-monitors and client sizes, etc. because someone proposed to
> automatically detect when desktop is restoring frames in a different
> display/monitor configuration and make sure that the frames were
> visible.
> 
> But, OTOH, it is entirely possible that the user is saving the desktop
> with some frames only partially visible. If you have many, and some of
> them are less used, you can set them aside so only a fraction of the
> frame is shown, which makes them accessible without taking too much
> screen space. So, IMO, the only thing that makes sense is to
> move/resize a frame while restoring when that frame is entirely
> outside the current viewing area. Or, perhaps, when the caption is
> (because in many/most/all? window managers, you can mouse-drag a
> window only from its caption).
> 
> Of course, there's no way to know the caption height (in pixels) from
> inside Emacs, I think, so in the end it's all an ugly heuristics: the
> top of the frame is some arbitrary number of pixels inside the viewing
> area. Or is there a better way?
> 

W32 is the odd duck here, frame-parameter top in NS and X refers to the outer 
edge of the window including caption height, i.e. the real top of the frame.  
We do know caption height in Emacs, but only at the C level.  W32 has to be 
fixed to behave like the other ports if it does not already.

        Jan D.