[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Proposed function: x-display-usable-bounds

From: YAMAMOTO Mitsuharu
Subject: Re: Proposed function: x-display-usable-bounds
Date: Mon, 03 Dec 2007 23:36:56 +0900 (JST)

>>>>> On Mon, 3 Dec 2007 15:34:57 +0300, "Adrian Robert" <address@hidden> said:

> On Dec 3, 2007 12:40 PM, Jan Djärv <address@hidden> wrote:
>> The implementation for KDE and Gnome could easily be done in elisp.
>> Does your patch handle multiple desktops/screens?

> For the Cocoa port (unsure about Carbon), screens throughout are
> currently considered separate display areas; dimensions reported for
> this and other x-display- functions correspond to the screen the
> frame being asked about is on, or the main screen (where menubar and
> dock are) if this information is not given.  (Other behaviors are
> possible, but not necessarily preferable.)

The behavior of x-display-pixel-width/height in the Carbon port was
changed relatively recently (March, 2007): it now reports the
dimensions of the whole screen because this behavior is more
consistent with the X11 build.


>> Isn't that the duty of the window manager?

> On the Mac (or GNUstep) there is no auto-placement of windows.

The Carbon(+AppKit) ports place a new frame to the cascading position
with respect to the selected frame if the position is not specified
explicitly.  Both Carbon and Cocoa have support for this functionality
(RepositionWindow and -[NSWindow cascadeTopLeftFromPoint:],
respectively).  Both of them also do rollover so that more than half
of the window (Carbon) or whole part of the window (Cocoa) becomes

                                     YAMAMOTO Mitsuharu

reply via email to

[Prev in Thread] Current Thread [Next in Thread]