I have a situation where a user might have a great many information windows
open at the same time (like the situation in Finder where you can click on a
file and select 'Get Info' ad infinitum.)
In order handle this situation, and so that I can still update each Window
individually, I decided
On 5 Apr 2013, at 13:38, Pax wrote:
I have a situation where a user might have a great many information windows
open at the same time (like the situation in Finder where you can click on a
file and select 'Get Info' ad infinitum.)
In order handle this situation, and so that I can still
On 5 Apr 2013, at 14:20, Mike Abdullah cocoa...@mikeabdullah.net wrote:
For a start, trying to access instance variables directly is almost always a
bad idea. Expose proper accessor methods instead.
Why is it a bad idea? I do this quite often, and I find it has the double
benefit of
On 5 Apr 2013, at 14:55, Pax 45rpmli...@googlemail.com wrote:
On 5 Apr 2013, at 14:20, Mike Abdullah cocoa...@mikeabdullah.net wrote:
For a start, trying to access instance variables directly is almost always a
bad idea. Expose proper accessor methods instead.
Why is it a bad idea? I
Ah, I see. I shall try that out. And, referring to my earlier question, would
I be able to:
[[device objectForKey:@InformationWindowRef].infoWindow
cascadeTopLeftFromPoint:NSMakePoint(20,20)];
On 5 Apr 2013, at 15:00, Tom Davie tom.da...@gmail.com wrote:
The reason it's a bad idea is
…And how would I make '@property (assign, nonatomic) NSWindow* iWindow;' an
IBOutlet so that I can hook it up to my window in interface builder?
On 5 Apr 2013, at 15:00, Tom Davie tom.da...@gmail.com wrote:
The reason it's a bad idea is because it means that you have two strongly
coupled
1) yes you could use the code you outlined to access the property
2) @property (assign, nonatomic) IBOutlet NSWindow *iWindow;
Note though to be careful about the assign tag there – you may well want that
to be a retain.
Thanks
Tom Davie
On 5 Apr 2013, at 15:06, Pax 45rpmli...@googlemail.com
I never retain IBOutlet properties. The view retains the object when it is
added, so also retaining the property would increase the retain count to 2.
I have not encountered a condition where I was required to access an
IBOutlet property after the view had been unloaded, so this approach has
On 5 Apr 2013, at 16:54, Joseph Dixon s...@dixondata.com wrote:
I never retain IBOutlet properties. The view retains the object when it is
added, so also retaining the property would increase the retain count to 2.
This assumes that the property you're talking about is a view, and that it's
On Fri, Apr 5, 2013 at 10:55 AM, Tom Davie tom.da...@gmail.com wrote:
This assumes that the property you're talking about is a view, and that
it's a subview of another view that's retained. The issue isn't quite as
simple as never retain IBOutlets.
Tom,
You are right, of course. Most
On Apr 5, 2013, at 7:03 AM, Pax 45rpmli...@googlemail.com wrote:
Ah, I see. I shall try that out. And, referring to my earlier question,
would I be able to:
[[device objectForKey:@InformationWindowRef].infoWindow
cascadeTopLeftFromPoint:NSMakePoint(20,20)];
No, because -objectForKey:
11 matches
Mail list logo
