Setting NSWindow to be transparent

I am trying to set NSWindow (borderless, with no controls) to be transparent before I display it (so that I can fade it onto the screen). Unfortunately, I don't seem to be able to - it loads, visibly, then sets the opacity to 0 (resulting in the window flickering at full opacity, before disappe

Re: Setting NSWindow to be transparent

I'm using the same effect in my application. The problem is, if you use this method, the window might not be there yet. Did you inspect if the window iVar is actually not nil? The way I did it is using the windowDidLoad method and call -(void)windowDidLoad { [super windowDidLoad]

Re: Setting NSWindow to be transparent

Forget what I said. If the value takes effect, window isn't nil. The trick is to uncheck "show window on launch". If I chekc that box, my window is visible at first too. - Michael On 16.06.2013, at 10:33, Michael Starke wrote: > I'm using the same effect in my application. > > The problem i

Re: Accelerate Framework?

Hi Rick, > Where to go for questions about the Accelerate Framework? I have a fairly good knowledge of the Accelerate framework and its opensource counterpart, Atlas. If I might be of any help, don’t hesitate. Vincent ___ Cocoa-dev mailing list (Co

Re: Setting NSWindow to be transparent

I've done those things already in my experimentation. Trouble is, my window is for a different window controller - not Application Delegate - and the window loads when the class does. Show Window On Launch doesn't seem to make any difference. On 16 Jun 2013, at 09:33, Michael Starke wrote:

Re: Accelerate Framework?

On Sat, 15 Jun 2013 13:33:20 -0700, Rick Mann said: >Where to go for questions about the Accelerate Framework? Sean ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do no

Re: popup menus and toolbar buttons

On 15 Jun 2013, at 19:33, Eric Smith wrote: > Anyone know how to attach a popup menu to a toolbar button, as with the 'run' > button in Xcode? I want to give users a choice of action via a popup menu if > they hold down one of my toobar buttons. I have code for doing this here: https://bitb

Re: popup menus and toolbar buttons

If you have an NSSegmentedControl with only one segment and a menu, the menu only pops up if you press and hold the button, otherwise it acts like a normal button. That sounds like what you want. - Original Message - From: "Eric Smith" To: cocoa-dev@lists.apple.com Sent: Saturday, June

Re: popup menus and toolbar buttons

On 16 Jun 2013, at 18:39, Lee Ann Rucker wrote: > If you have an NSSegmentedControl with only one segment and a menu, the menu > only pops up if you press and hold the button, otherwise it acts like a > normal button. That sounds like what you want. Ooh, that's a good one to know, thanks! _

Re: Multiple Observations

You have a valid point. However, awakeFromNib is a traditional place to setup observers, etc. Plus, the docs even recommend this: ³Important: It is possible that your datasource methods for populating the outline view may be called before awakeFromNib is called if the datasource is specified in

Full-height toolbar items

I'm working on a library for doing full-height toolbar items, like the center status display in Instruments, Xcode, and iTunes. I'm not completely finished yet, but I have reached a point where I'd like to share it. Feedback is welcome. https://github.com/Uncommon/UUFullHeightToolbar ___

Confused by memory issue with UIDatePicker

Dear List, I am using manual retain count memory management (started long before ARC was available) for an iOS app. I have a UIDatePicker in an .xib file with its File's Owner set to a custom class, MyTimeDatePickerVC. The MyTimeDatePickerVC inherits from UIViewController, and has an IBOutlet a

Confused by memory issue with UIDatePicker

Sorry, I should have been more precise: The problem is progressive memory growth each time the ViewController is displayed. If I add the [release], the memory footprint reverts to its pre-viewcontroller display level each time the VC is dismissed. -Dan ___

Re: Confused by memory issue with UIDatePicker

On Jun 16, 2013, at 15:30 , Daniel Wambold wrote: > I have a UIDatePicker in an .xib file with its File's Owner set to a custom > class, MyTimeDatePickerVC. The MyTimeDatePickerVC inherits from > UIViewController, and has an IBOutlet attached to the UIDatePicker. What does the IBOutlet declara

Re: Confused by memory issue with UIDatePicker

Quincey Morris wrote: > >> I have a UIDatePicker in an .xib file with its File's Owner set to a custom >> class, MyTimeDatePickerVC. The MyTimeDatePickerVC inherits from >> UIViewController, and has an IBOutlet attached to the UIDatePicker. > > What does the IBOutlet declaration for the UIDateP

Re: Confused by memory issue with UIDatePicker

On Sun, Jun 16, 2013, at 05:00 PM, Daniel Wambold wrote: > Quincey Morris wrote: > > > >> I have a UIDatePicker in an .xib file with its File's Owner set to a > >> custom class, MyTimeDatePickerVC. The MyTimeDatePickerVC inherits from > >> UIViewController, and has an IBOutlet attached to the UI

Re: Confused by memory issue with UIDatePicker

Kyle Sluder wrote: > On Sun, Jun 16, 2013, at 05:00 PM, Daniel Wambold wrote: >> Quincey Morris wrote: >>> I have a UIDatePicker in an .xib file with its File's Owner set to a custom class, MyTimeDatePickerVC. The MyTimeDatePickerVC inherits from UIViewController, and has an IBO

Re: Confused by memory issue with UIDatePicker

On Jun 16, 2013, at 17:29 , Kyle Sluder wrote: > For this reason, that document recommends you use a weak declared > property for outlets to non-top-level objects. You should probably > follow that recommendation. Under the circumstances, since this is a manual RR app, just releasing the UIDat

Re: Confused by memory issue with UIDatePicker

On Jun 16, 2013, at 6:08 PM, Quincey Morris wrote: > On Jun 16, 2013, at 17:29 , Kyle Sluder wrote: > >> For this reason, that document recommends you use a weak declared >> property for outlets to non-top-level objects. You should probably >> follow that recommendation. > > > Under the circ

Re: IB keeps changing my constraints when I resize the cell

On Jun 15, 2013, at 20:00 , Quincey Morris wrote: > On Jun 15, 2013, at 19:31 , Rick Mann wrote: > >> There's a setting for "Automatic"…where does it get it from then? > > AFAIK, it means the row height is set automatically based on the control size > (small/medium/large). Ah, I see. They

Re: Confused by memory issue with UIDatePicker

On Jun 16, 2013, at 18:16 , Kyle Sluder wrote: > Meh. As a Mac programmer, your approach would indeed be my instinct, but I'm > trying to train myself to be more modern. Better still, it occurred to me after posting, would be to use Refactor… to convert the app to ARC. That would be even more

Re: Confused by memory issue with UIDatePicker

> On Jun 16, 2013, at 9:08 PM, Quincey Morris wrote: > > On Jun 16, 2013, at 17:29 , Kyle Sluder wrote: > >> For this reason, that document recommends you use a weak declared >> property for outlets to non-top-level objects. You should probably >> follow that recommendation. > > Under the circu

Causes of "Cannot update object that was never inserted"

About once a month, I get a report from a user indicating that my app raised an exception, "Cannot update object that was never inserted". Last week I got two of these, so I'm looking harder to try and find the cause. I presume this "object" is a Core Data managed object. From reading on this

Re: Causes of "Cannot update object that was never inserted"

I believe that ALAssetLibrary uses Core Data, so the problem could be a user's messed up image library. Having just been through hell due to a corrupted iTunes library on my device, I can say that such problems can lead to very inconsistent behavior. Julian -- Julian Richardson, PhD www.terna

Re: Causes of "Cannot update object that was never inserted"

On 2013 Jun 16, at 22:22, Julian Richardson wrote: > I believe that ALAssetLibrary uses Core Data, so the problem could be a > user's messed up image library. Thank you, Julian. I don't think that's the problem here. The error logged indicates that the object's entity is one of "my" entitie