(reposted because of an apparent bounce)
On Aug 2, 2012, at 22:16 , Erik Stainsby erik.stain...@roaringsky.ca wrote:
I do so wish there was a Complete Idiot's Guide to Cocoa Table Bindings … The
very flexibility which I know must be their great virtue tends to obscure the
clear path from my
On Aug 2, 2012, at 10:16 PM, Erik Stainsby erik.stain...@roaringsky.ca wrote:
I do so wish there was a Complete Idiot's Guide to Cocoa Table Bindings … The
very flexibility which I know must be their great virtue tends to obscure the
clear path from my sight more often than not. Forest,
On Aug 3, 2012, at 12:11 AM, Kyle Sluder k...@ksluder.com wrote:
You should consider using a view-based table view if you're targeting 10.7 or
later. They're so much nicer!
Hmm, now that Quincy's pointed it out, it looks like you are indeed using a
view-based table view. That will make
On Aug 3, 2012, at 12:11 AM, Kyle Sluder k...@ksluder.com wrote:
You should consider using a view-based table view if you're targeting 10.7 or
later. They're so much nicer!
Hmm, now that Quincy's pointed it out, it looks like you are indeed using a
view-based table view. That will make
On Aug 3, 2012, at 00:16 , Kyle Sluder k...@ksluder.com wrote:
Hmm, now that Quincy's pointed it out, it looks like you are indeed using a
view-based table view.
No bonus points to me though. Having cleverly focused on the forest instead of
the trees, I didn't register the fact that using
Hi List,
I've been reworking my application and I've found a solution I'm not
particularly happy with, and was hoping to get some advice from others.
I have several views that are essentially views onto different tables. Each
row in the table represents real items in the file system (because
On 03/08/2012, at 5:56 PM, Arved von Brasch co...@atgo.org wrote:
I've settled on having the array controller publish values and having the
view controller notice by key-value observing.
Sounds reasonable. Is there a problem with this approach?
--Graham
Erik,
I've only made a custom subclass of NSArrayController once and that was a long
time a go to do some custom thing that I don't remember now.
Normally I add an array to the appropriate view controller that has the table
data in it and then bind the NSArrayController's content to that array.
On 2012-08-03, at 18:04 , Graham Cox graham@bigpond.com wrote:
On 03/08/2012, at 5:56 PM, Arved von Brasch co...@atgo.org wrote:
I've settled on having the array controller publish values and having the
view controller notice by key-value observing.
Sounds reasonable. Is there a
Hi all,
ML introduces +[NSColor underPageBackgroundColor];
I had thought this was to be the grey linen texture as used in Mail, etc but
instead I'm getting a sort of flat pale cream colour. Is that right?
--Graham
___
Cocoa-dev mailing list
Thank you gentlemen, both, for taking the time to educate me. I have lots to
rethink in my design, such as it was.
On 2012-08-03, at 12:27 AM, Quincey Morris
quinceymor...@rivergatesoftware.com wrote:
On Aug 3, 2012, at 00:16 , Kyle Sluder k...@ksluder.com wrote:
Hmm, now that Quincy's
Hello,
About seven years ago someone had figured out how to load and call frameworks
from inside a System Prefs Pane plugin, I've used that technique for a solution
for a client ever since.
They never jumped on 10.7 for numerous reasons, but now we need to prepare to
move to 10.8, late I know
My app, created in Lion but targeting SL seems to work fine except that, when
actually run in Snow Leopard, it crashes whenever Open or Open Recent is
selected. The crash log gives
0 com.apple.AppKit 0x7fff885e49de -[NSImage
_allocAuxiliaryStorage] + 158
1
I have a subclass of UIViewController which displays a small view in the center
of the display.
shouldAutorotateToInterfaceOrientation: returns YES.
The problem:
when I rotate the device, the centered view rotates as it should. But it also
changes its size to full-screen.
The (bad) workaround:
On Aug 3, 2012, at 8:34 AM, Gerriet M. Denkmann gerr...@mdenkmann.de wrote:
I have a subclass of UIViewController which displays a small view in the
center of the display.
shouldAutorotateToInterfaceOrientation: returns YES.
The problem:
when I rotate the device, the centered view rotates
On 3 Aug 2012, at 22:50, David Duncan wrote:
On Aug 3, 2012, at 8:34 AM, Gerriet M. Denkmann gerr...@mdenkmann.de wrote:
I have a subclass of UIViewController which displays a small view in the
center of the display.
shouldAutorotateToInterfaceOrientation: returns YES.
The problem:
I have a subclass of UIViewController which displays a small view in the center
of the display.
shouldAutorotateToInterfaceOrientation: returns YES.
This view is only shown on demand.
The problem:
If the device is in Portrait-Up position when the ViewController is created
then everything is
On Aug 3, 2012, at 9:16 AM, Gerriet M. Denkmann gerr...@mdenkmann.de wrote:
The code in basicView (an UIView) is:
- (void)touchesEnded:(NSSet *)touches withEvent:(UIEvent *)event
{
if ( self.sliderView == nil ) // load nib
{
NSBundle *mainBundle = [
On Aug 3, 2012, at 9:22 AM, Gerriet M. Denkmann gerr...@mdenkmann.de wrote:
I have a subclass of UIViewController which displays a small view in the
center of the display.
shouldAutorotateToInterfaceOrientation: returns YES.
This view is only shown on demand.
The problem:
If the
On 3 Aug 2012, at 23:59, David Duncan wrote:
On Aug 3, 2012, at 9:16 AM, Gerriet M. Denkmann gerr...@mdenkmann.de wrote:
The code in basicView (an UIView) is:
- (void)touchesEnded:(NSSet *)touches withEvent:(UIEvent *)event
{
if ( self.sliderView == nil ) // load nib
On Aug 3, 2012, at 10:39 AM, Gerriet M. Denkmann gerr...@mdenkmann.de wrote:
1) adopt view controller containment and do this addition in the view
controller that owns basicView (which needs to be a subclass to do this
properly) of
If I understand this correctly, I have to do:
create a
NSTime docs say:
--
The date at which the receiver will fire. If the timer is no longer valid,
this method returns the last date at which the timer fired.
--
For an invalidated timer I am seeing a fireDate of: 2001-01-01 00:00:00
But I know it fired at 2012-08-03 19:39:12
Is this a known bug?
On Aug 3, 2012, at 3:00 PM, Graham Cox graham@bigpond.com wrote:
Hi all,
ML introduces +[NSColor underPageBackgroundColor];
I had thought this was to be the grey linen texture as used in Mail, etc but
instead I'm getting a sort of flat pale cream colour. Is that right?
--Graham
NSTimer* myTimer = [NSTimer scheduledTimerWithTimeInterval:60 target:self
selector:@selector(wantsUpdate:) userInfo:nil repeats:NO]
Sometime after it fires (and occasionally before), I call
if ( myTimer )
{
[myTimer invalidate];
[myTimer release];
myTimer = nil;
}
Should I really be
That color is actually a pattern. What are you doing that gives you the
unexpected result?
--
Gary L. Wade (Sent from my iPhone)
http://www.garywade.com/
On Aug 3, 2012, at 1:14 PM, Marcus Karlsson m...@acc.umu.se wrote:
On Aug 3, 2012, at 3:00 PM, Graham Cox graham@bigpond.com wrote:
You must use the 2nd way. If you don't you could get a memory exception if the
timer has fired and, therefore, been invalidated.
On Aug 3, 2012, at 4:19 PM, Trygve Inda wrote:
NSTimer* myTimer = [NSTimer scheduledTimerWithTimeInterval:60 target:self
selector:@selector(wantsUpdate:)
On Fri, 3 Aug 2012 23:00:26 +1000, Graham Cox said:
ML introduces +[NSColor underPageBackgroundColor];
I had thought this was to be the grey linen texture as used in Mail, etc
but instead I'm getting a sort of flat pale cream colour. Is that right?
I think it's supposed to be the colour related
Not if you've retained the timer - and if you haven't, then you shouldn't
release it. Conversely if you *have*, you should release and nil it when it
fires.
On Aug 3, 2012, at 2:10 PM, Charlie Dickman wrote:
You must use the 2nd way. If you don't you could get a memory exception if
the
You must use the 2nd way. If you don't you could get a memory exception if the
timer has fired and, therefore, been invalidated.
On Aug 3, 2012, at 4:19 PM, Trygve Inda wrote:
My code looks like this:
-(void)awakeFromNib
{
[self setUpdateTimer:[NSTimer
On 04/08/2012, at 6:55 AM, Gary L. Wade garyw...@desisoftsystems.com wrote:
That color is actually a pattern. What are you doing that gives you the
unexpected result?
I'm expecting it to be a pattern, with a fairly obvious linen texture.
I get the colour and i use it to -setBackgroundColor:
On Aug 3, 2012, at 14:37 , Trygve Inda cocoa...@xericdesign.com wrote:
I think B is the concern since if I
change the code to:
if ([updateTimer isValid])
[updateTimer invalidate];
Then it will be invalidated in case B (because the code has not fallen back
to the run loop to invalidate
31 matches
Mail list logo
