[bug #17377] Various frame related methods in NSWindow return wrong results

[Quentin Mathé]

Follow-up Comment #7, bug #17377 (project gnustep):

In my previous entry, I wrote incorrect statements about frameRect and
contentRect, I thought windowFrame and frameRect were totally unrelated by
reading the following method name.

/*
Internal helpers.

Returns the internal window frame rect for a given (screen) frame.
*/
+(NSRect) windowFrameRectForFrameRect: (NSRect)aRect
                            styleMask: (unsigned int)aStyle
{
  aRect.origin = NSZeroPoint;
  return aRect;
}

windowFrame is basically just the frameRect with a zero origin. Is this just
the same as the bounds rectangle returned by [window bounds]?

So… Here is a corrected version of my summary:

- screenRect == frameRect on Cocoa/OpenStep
- contentRect == contentRect on Cocoa/OpenStep
- frameRect (windowFrame with a non zero origin) == frameRect or contentRect
on Cocoa/OpenStep (since it represents the frame manipulated in the backend)

In other words, the frameRect returned by [window frame] can be equal to
either screenRect (when GSX11HandlesWindowDecorations=NO) or contentRect
(when GSX11HandlesWindowDecorations=YES)

Hopes I haven't done any new misunderstandings,
Quentin.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?17377>

_______________________________________________
  Message posté via/par Savannah
  http://savannah.gnu.org/