RE: set/saveFrameUsingName
RE: set/saveFrameUsingName
- Subject: RE: set/saveFrameUsingName
- From: Jeremy Dronfield <email@hidden>
- Date: Fri, 5 Jul 2002 11:02:10 +0100
On Thursday, July 4, 2002, at 11:05 pm, Nicholas Riley wrote:
>
On Thu, Jul 04, 2002 at 11:00:11PM +0100, Jeremy Dronfield wrote:
>
> Thanks. I tried some of the workarounds (the ones that seemed suitable)
>
> and also did some experiments. I found that using
>
> -setWindowFrameAutosaveName: instead of -setFrameAutosaveName: in
>
> -awakeFromNib overcame the problem, but only partially. It works only
>
> so
>
> long as the right hand edge of the window doesn't come closer than
>
> about
>
> an inch (about 50-80 pixels) to the right hand edge of the screen.
>
> Since
>
> this bug doesn't seem to affect Apple's own Cocoa apps (e.g. the
>
> Activity Viewer in Mail, which I'm looking at right now), I don't
>
> understand why it's affecting mine.
>
>
The activity viewer is resizable, so it works. The bug only shows up
>
for windows which are nonresizable, which is probably the case with
>
your window.
No, my window IS resizable. Maybe I'm getting a different bug.
I noticed another thing in my experiments: that (contrary to what I said
in my first post) the window does NOT open to its default position (the
default determined by its placement in Interface Builder), but to a
position on the far left of the screen. Later, it occurred to me that
the "forbidden zone" on the right hand edge of the screen is the area
the dock would occupy if it were unhidden and set to that edge. So, my
inference is that a bug is causing the system to tell my application
"You can't put your window there - that's where the dock is." (It
isn't - I keep my dock hidden on the bottom edge.) The app then looks
for the edge of the dock. It can't find it, because it isn't there, and
decides to play safe (or falls victim to an algorithm which misfires due
to false information provided by the system) and puts the window on the
far left of the screen.
I'm only guessing with this interpretation, but since
-setWindowFrameAutosaveName: saves and sets position and size
information perfectly as long as the window stays out of that bad zone,
it seems the most likely. Do you (or anyone else) have any
ideas/explanations?
- Jeremy.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.