Set the size of a sheet when it's first loaded

2016-08-25 Thread Shane Stanley
I have a window that is shown as a sheet over another window. The sheet contains a small table, and I want the sheet to be sized vertically to show however many rows are required. So just before I show the sheet I update the table and adjust the window's frame. This works fine -- except for the

runModalForWindow() doesn't re-activate former window upon return

2016-08-25 Thread Andreas Falkenhahn
Isn't runModalForWindow() supposed to activate the window which formerly had the focus when it returns? It doesn't do this here. When runModalForWindow() returns, the window that was active when I called runModalForWindow() isn't made active again. Of course, I could do this manually by calling m

Re: Set the size of a sheet when it's first loaded

2016-08-25 Thread Sandor Szatmari
Shane, > On Aug 25, 2016, at 04:28, Shane Stanley wrote: > > I have a window that is shown as a sheet over another window. The sheet > contains a small table, and I want the sheet to be sized vertically to show > however many rows are required. So just before I show the sheet I update the

Re: Set the size of a sheet when it's first loaded

2016-08-25 Thread Shane Stanley
On 25 Aug 2016, at 10:22 PM, Sandor Szatmari wrote: > > What are you calling to set the window's frame? I am under the impression > that calling setFrame: is not respected when using autolayout. Thanks -- that's the simple thing I was forgetting. -- Shane Stanley ,

Re: Core Graphics: Is it better to up-sample or down-sample images when drawing into a rect?

2016-08-25 Thread Steve Christensen
> On Aug 24, 2016, at 8:37 PM, Jeff Szuhay wrote: > > >> On Aug 24, 2016, at 8:02 PM, Britt Durbrow >> wrote: >> >> >>> On Aug 24, 2016, at 12:59 PM, Jeff Szuhay wrote: >>> >>> I draw my images (clocks) into a “reference” sized rectangle—for simplified >>> position calculations—and then h

Re: runModalForWindow() doesn't re-activate former window upon return

2016-08-25 Thread Ken Thomases
On Aug 25, 2016, at 6:51 AM, Andreas Falkenhahn wrote: > > Isn't runModalForWindow() supposed to activate the window which formerly > had the focus when it returns? It doesn't do this here. When > runModalForWindow() > returns, the window that was active when I called runModalForWindow() > isn't

Re: runModalForWindow() doesn't re-activate former window upon return

2016-08-25 Thread Andreas Falkenhahn
On 25.08.2016 at 17:21 Ken Thomases wrote: > On Aug 25, 2016, at 6:51 AM, Andreas Falkenhahn > wrote: >> Isn't runModalForWindow() supposed to activate the window which formerly >> had the focus when it returns? It doesn't do this here. When >> runModalForWindow() >> returns, the window that w

Re: runModalForWindow() doesn't re-activate former window upon return

2016-08-25 Thread Keary Suska
> On Aug 25, 2016, at 9:45 AM, Andreas Falkenhahn > wrote: > > Tested it, the window is clearly main and key, this is the debug output: > > CHECK: 0x10040b4d0 0x10040b4d0 0x10040b4d0 > > i.e. [NSApp mainWindow], [NSApp keyWindow] and my NSWindow pointer are > exactly the same before runModalF

Re: runModalForWindow() doesn't re-activate former window upon return

2016-08-25 Thread Andreas Falkenhahn
On 25.08.2016 at 19:47 Keary Suska wrote: >> On Aug 25, 2016, at 9:45 AM, Andreas Falkenhahn >> wrote: >> Tested it, the window is clearly main and key, this is the debug output: >> CHECK: 0x10040b4d0 0x10040b4d0 0x10040b4d0 >> i.e. [NSApp mainWindow], [NSApp keyWindow] and my NSWindow pointe

Re: runModalForWindow() doesn't re-activate former window upon return

2016-08-25 Thread Kyle Sluder
On Thu, Aug 25, 2016, at 01:51 PM, Andreas Falkenhahn wrote: > On 25.08.2016 at 19:47 Keary Suska wrote: > > >> On Aug 25, 2016, at 9:45 AM, Andreas Falkenhahn > >> wrote: > > >> Tested it, the window is clearly main and key, this is the debug output: > > >> CHECK: 0x10040b4d0 0x10040b4d0 0x