On Mar 13, 2013, at 18:26:01, Seth Willits <sli...@araelium.com> wrote:
> On Mar 13, 2013, at 8:34 AM, Ken Thomases wrote: > >> The Window Server moves most windows entirely without involving the app >> (until the move is completed). > > Minor detail… while the window is being moved the app has no idea it's > happening, but after the movement stops for some brief time (the mouse button > can *still be held down*) the window's frame is changed. That is, while the > mouse button is held down, the window frame *does* update, but only after the > mouse has stopped moving for some short amount of time. The frame change > happens transparently though — no calls to any setFrame method is made (and > no notifications happen etc). So it's still useless, but it's interesting. > >> If you want to change how windows get moved, I think you have to take over >> the whole process. You do [window setMovable:NO] to make the Window Server >> not move your windows itself. Instead, you get the relevant mouse events >> and you write typical mouse drag code and change the window frame manually. >> See the docs for -[NSWindow isMovable]. > > I too think this the only option. Thanks for the thoughtful and wise responses. Looks like I'll be writing code that Apple neglected to write for Cocoa, when it was readily available in Carbon. -- Steve Mills office: 952-818-3871 home: 952-401-6255 cell: 612-803-6157 _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
