Re: NSDrawer

have a fixed-size layout, so the window > is also a fixed size. No full screen mode: it would just look weird. > > We can't put the extra info in front of the main layout because users need to > see both. NSSplitView would be half-empty most of the time. > > NSDrawer is

Re: NSDrawer

also a fixed size. No full screen mode: it would just look weird. We can't put the extra info in front of the main layout because users need to see both. NSSplitView would be half-empty most of the time. NSDrawer is working great, and hopefully it won't be removed despite the deprecation.

Re: NSDrawer

dev-requ...@lists.apple.com > > You can reach the person managing the list at > cocoa-dev-ow...@lists.apple.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Cocoa-dev digest..." > Today's Topics: >

Re: NSDrawer

>>  FWIW, the deprecation warning for NSDrawer says to "consider using  >>NSSplitViewController." I can see how NSSplitViewController might be a good replacement in some cases, but not here. Thanks for all the suggestions, Casey McDerm

Re: NSDrawer

Hi Cocoa-dev people, FWIW, the deprecation warning for NSDrawer says to "consider using NSSplitViewController." Best regards, Joel Norvell On Mon, Jul 2, 2018, at 7:08 PM, Casey McDermott wrote: > NSDrawer is deprecated, but it's also perfect for our application. > We sti

Re: NSDrawer

Casey McDermott wrote: > NSPanel is still modal, but longer lasting. We use it a lot, and it > looks better than the modal dialogs in the current app. I read in digest mode so maybe this has already been pointed out, but NSPanel is not modal. ___

Re: NSDrawer

The way I see it, NSPopover is best for ephemeral extra details. We may use it in a few places, but it won't replace NSDrawer. NSPanel is still modal, but longer lasting. We use it a lot, and it looks better than the modal dialogs in the current app. NSDrawer is a non-modal extension

Re: NSDrawer

Just for completeness' sake: You're aware of NSPopover? > On 3. Jul 2018, at 04:08, Casey McDermott wrote: > > NSDrawer is deprecated, but it's also perfect for our application. > We still haven't found a good substitute. > > Our app has an outline view that loads various

Re: NSDrawer

Thanks for all the useful suggestions. We need to use a child window in the Windows app, since MFC does not have anything like drawers. If necessary we can use the same approach on Mac. But, maybe we'll get lucky and NSDrawer won't die. It only takes a few lines of code, and it is just

Re: NSDrawer

On 3 Jul 2018, at 03:08, Casey McDermott wrote: > > NSDrawer is deprecated, but it's also perfect for our application. > We still haven't found a good substitute. [snip] > Is there a work-around for an attached window that pops out on the side, > and acts like a drawer?

Re: NSDrawer

I think the best I've seen design wise is with the Safari browser itself. Show/hide the sidebar (Shift-Cmd-L or View -> Show Sidebar) to see how it could work (your main view will have to do some smart resizing). On Tue, Jul 3, 2018 at 10:08 AM Casey McDermott wrote: > NSDrawer is depr

NSDrawer

NSDrawer is deprecated, but it's also perfect for our application. We still haven't found a good substitute. Our app has an outline view that loads various types of business records into a tab view. Some of them have optional extra info. When it's small a panel is fine, but some records have

Re: -[NSWindow makeFirstResponder:] error when NSDrawer is involved

> 2017/03/25 3:04、Bill Cheeseman wrotes： > > Has anybody else encountered this issue? Any suggestions? I got the same error message even the drawer is hidden. I set my custom control as the first responder in a dialog window just after loading xib. I could not rid

Re: -[NSWindow makeFirstResponder:] error when NSDrawer is involved

> On Mar 24, 2017, at 3:53 PM, Quincey Morris > wrote: > > On Mar 24, 2017, at 11:04 , Bill Cheeseman > wrote: >> >> Any suggestions? > > No good ones, but you keep referring to the “main”

Re: -[NSWindow makeFirstResponder:] error when NSDrawer is involved

On Mar 24, 2017, at 11:04 , Bill Cheeseman wrote: > > Any suggestions? No good ones, but you keep referring to the “main” window. Is it possible that the drawer window is initially the key window, and this is interfering with setting the first responder? Can you

-[NSWindow makeFirstResponder:] error when NSDrawer is involved

The principal view in my application's main window is a browser view. I want to make the browser view the main window's first responder. My application also has a drawer associated with the main window. The first time -[NSWindow makeFirstResponder:] is called on the main window to make its

NIBs combining NSTabView and NSDrawer

I’m working on a program that does digital signal processing on the audio tracks of a Quicktime Movie. I have a NSWindow that has a NSTabView. The window has some drawers that open when one of the tabs is clicked on. One of the tabs draws a digital oscilloscope, another draws graphs and a

Re: NIBs combining NSTabView and NSDrawer

On 7 Nov 2013, at 5:46 pm, Joseph Ayers j.ay...@neu.edu wrote: I’m working on a program that does digital signal processing on the audio tracks of a Quicktime Movie. I have a NSWindow that has a NSTabView. The window has some drawers that open when one of the tabs is clicked on. One of

Re: NIBs combining NSTabView and NSDrawer

On Nov 7, 2013, at 08:46 , Joseph Ayers j.ay...@neu.edu wrote: I have a NSWindow that has a NSTabView. The window has some drawers that open when one of the tabs is clicked on. One of the tabs draws a digital oscilloscope, another draws graphs and a third some DSP graphics The drawers

Re: NSDrawer not always sending -drawerDidOpen: to delegate

For archive searchers, this non-reproducible problem that we worked on 3 weeks ago wasn't fixed. It happened to me again yesterday. Also, another, probably related problem occurred, which is that a bunch of checkboxes in the drawer, created and bound programatically, seemed to lose their

Re: NSDrawer not always sending -drawerDidOpen: to delegate

OK, so while the drawer was in the broken state again, with the delegate wired in the nib, I poked it with the debugger again and found that, in order to fix it, I must first set the drawer's delegate to nil before setting it back to the window controller. That is, this did not work: (lldb)

NSDrawer not always sending -drawerDidOpen: to delegate

) $0 = 0x000108213bc0 InspectorController: 0x108213bc0 (lldb) po [$0 window] (id) $1 = 0x000108186bc0 NSPanel: 0x108186bc0 (lldb) po [$1 drawers] (id) $2 = 0x000100d3c4b0 __NSArrayI 0x100d3c4b0( NSDrawer: 0x10829e840, NSDrawer: 0x108254e30 ) … Sent more messages to drawer's content

Re: NSDrawer not always sending -drawerDidOpen: to delegate

On Feb 16, 2013, at 5:31 PM, Jerry Krinock je...@ieee.org wrote: In an app running in Mac OS X 10.8, I have set a drawer's delegate to be its window controller, in the window controller's -awakeFromNib… - (void)awakeFromNib { … [drawer setDelegate:self] ; … } Any reason you

Re: NSDrawer not always sending -drawerDidOpen: to delegate

On 2013 Feb 16, at 18:24, Kyle Sluder k...@ksluder.com wrote: ;Any reason you didn't do this in the nib itself? Probably because I generally find it more enjoyable to write code rather than click and poke my way through Interface Builder. I'm wondering if you're hitting that caveat from the

Re: NSDrawer not always sending -drawerDidOpen: to delegate

On Feb 16, 2013, at 6:50 PM, Jerry Krinock je...@ieee.org wrote: On 2013 Feb 16, at 18:24, Kyle Sluder k...@ksluder.com wrote: ;Any reason you didn't do this in the nib itself? Probably because I generally find it more enjoyable to write code rather than click and poke my way through

NSDrawer dealloc causes kCGErrorIllegalArgument

in WindowData::Destruct () #7 0x9193b0cd in _CFRelease () #8 0x93c07e87 in -[NSWindow dealloc] () #9 0x93e0d951 in -[NSDrawer dealloc] () #10 0x9193af38 in CFRelease () #11 0x919655b2 in __CFArrayReleaseValues () #12 0x9193b101 in _CFRelease () #13 0x91967c6d in _CFAutoreleasePoolPop () #14

Re: NSDrawer dealloc causes kCGErrorIllegalArgument

() #5 0x90083d67 in WindowData::OnActiveSpace () #6 0x90083981 in WindowData::Destruct () #7 0x9193b0cd in _CFRelease () #8 0x93c07e87 in -[NSWindow dealloc] () #9 0x93e0d951 in -[NSDrawer dealloc] () #10 0x9193af38 in CFRelease () #11 0x919655b2 in __CFArrayReleaseValues () #12 0x9193b101

NSDrawer contentView clip

I have put some buttons within a drawer.contentView The top most button gets cut by 20 pixels because the contentView result shorter than its superview height. So, at the top of the drawer I always see a gray rectangle, 20 pixels height, where I can't draw in. Please, how can I use the whole

Key window/first responder handling with NSDrawer containing NSTextView

I have an NSDrawer on a window that acts as an optional 'pop out' editor providing a more convenient way to edit text in smaller field in the window's main UI. I've used the occasional drawer before in cases where optional extra information/navigation is useful, and aside from one bug I know

Re: Key window/first responder handling with NSDrawer containing NSTextView

-09, at 12:57 PM, Luke Evans wrote: I have an NSDrawer on a window that acts as an optional 'pop out' editor providing a more convenient way to edit text in smaller field in the window's main UI. I've used the occasional drawer before in cases where optional extra information/navigation

Re: Sizing strangeness in the land of NSDrawer

Hi Steve, Thanks for the reply. Ouch, yes, you're right, it works perfectly with GC turned off, and misbehaves with Required or Supported. This will be a major bummer if there's no workaround (I guess it will be bye-bye NSDrawer). So the obvious next question: is there a work around

Sizing strangeness in the land of NSDrawer

Hello list denizens. I've just created some UI with an NSDrawer attached to a regular window. I've done this before a while back and everything worked fine. I thought everything was fine this time too: the drawer opens on command, has the correct initial size, and behaves mostly normally

Re: Sizing strangeness in the land of NSDrawer

Turn on garbage collection and see if it starts working. -Steve On Oct 25, 2008, at 9:06 PM, Luke Evans wrote: Hello list denizens. I've just created some UI with an NSDrawer attached to a regular window. I've done this before a while back and everything worked fine. I thought

Re: Sizing strangeness in the land of NSDrawer

Typo, I meant turn off garbage collection and see if it starts working. oops -Steve On Oct 25, 2008, at 9:06 PM, Luke Evans wrote: Hello list denizens. I've just created some UI with an NSDrawer attached to a regular window. I've done this before a while back and everything

NSDrawer detached from window?

I'm wondering if anyone has seen this behavior before. I have a NSDrawer, which in IB has its parent window set to my document's main window, and the content view set appropriately. I can open and close the drawer fine, and also resize its width by dragging the drawer's border

Re: NSDrawer detached from window?

On Oct 9, 2008, at 8:20 AM, Mark Roseman wrote: I'm wondering if anyone has seen this behavior before. I have a NSDrawer, which in IB has its parent window set to my document's main window, and the content view set appropriately. I can open and close the drawer fine, and also resize its

Implementing NSHUDWindowMask on NSDrawer

Just for fun, I'm trying to implement an NSDrawer object with a HUD- style look'n'feel to it. As it turns out, it is not a subclass of NSWindow that lets me do what I need to do. If NSDrawer was that, it would be easy, otherwise, not so much. SO, here's my Q: (1) *Can* I implement

Re: NSDrawer resizing problem - no longer resizes when parent window resized

I found this message in the archives from a few months ago. In case anyone else runs into it, I discovered that it happens only when garbage collection is enabled. I filed Radar 5867411. I've an odd problem with a drawer in my application. I'm seeing the behavior on Leopard, but it could