Re: QuickTime Player - like application

2011-05-21 Thread Nick 
Dear list,
I am currently making an application that i would like to look like a quick
time player (as it actually may play movie files and may broadcast them -
this is a kind of a messenger).

That's why i need the same controls - play, pause, volume, etc in my
application.

Do you think that would be a bad idea to make it look identically (only
appearance, the functionality is completely different) to the original
QuickTime player?
>From the user's point of view, i would prefer an app  (or rather one window
in my case) that is similar to the player i already have (since it plays
movies).

I actually haven't seen a lot of players for Mac OS (apart from Quick Time
player and iTunes i am using VLC, but the last one uses QT and is not
supposed to look "native" enough).

Is QuickTime interface's idea somehow "protected" and the similarities are
not allowed by Apple developers?
If so, what player do you think looks the most native and you would prefer
to use if you didn't have QuickTime player? Or you don't care about what
does it look like, as long as it has these control play-pause-volume-etc
buttons?

Thanks
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: QuickTime Player - like application

2011-05-21 Thread Nick 
I forgot to say that this is now the whole application that 'copies'
quicktime, but only a single window that plays movies. The rest of my app
looks differently. I was making an analogy to the cocoa controls that the
users got used to and don't want to see anything "custom".
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Visually disabling some checkboxes in a NSTableView

2011-05-21 Thread Tito Ciuro 
Hello,

I have a table view which contains a column that displays checkboxes. I would 
like to disable and gray out some of the checkboxes, so I guess there are two 
possible ways (perhaps there's another way?):

1) disable the control (i.e. gray out) so that the user cannot toggle it (in 
one single method)
2) ignore tracking for the affected rows and disable the cell/control (in two 
or more methods)

I've tried option #2. I've implemented - 
(BOOL)tableView:shouldTrackCell:forTableColumn:row: and the click gets properly 
ignored. However, I'd also like to indicate to the user that the checkbox 
cannot be toggled, and this is where I'm stuck. How would some of these 
checkboxes be grayed out?

Thanks in advance,

-- Tito
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Visually disabling some checkboxes in a NSTableView

2011-05-21 Thread Kyle Sluder 
On Sat, May 21, 2011 at 9:19 AM, Tito Ciuro  wrote:
> Hello,
>
> I have a table view which contains a column that displays checkboxes. I would 
> like to disable and gray out some of the checkboxes, so I guess there are two 
> possible ways (perhaps there's another way?):
>
> 1) disable the control (i.e. gray out) so that the user cannot toggle it (in 
> one single method)

There is no checkbox control. The tableview uses one checkbox cell to
draw the entire column. So you can't just selectively disable checkbox
instances because there is only one checkbox.

Disable the cell in -tableView:willDisplayCell:forTableColumn:row:.
Alternatively, if you're using bindings, bind the table column's
"enabled" binding to a key that returns YES or NO as appropriate.

--Kyle Sluder
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Visually disabling some checkboxes in a NSTableView

2011-05-21 Thread Tito Ciuro 
Hi Kyle,

The method -tableView:willDisplayCell:forTableColumn:row: did the trick, thanks!

-- Tito

On May 21, 2011, at 10:02 AM, Kyle Sluder wrote:

> On Sat, May 21, 2011 at 9:19 AM, Tito Ciuro  wrote:
>> Hello,
>> 
>> I have a table view which contains a column that displays checkboxes. I 
>> would like to disable and gray out some of the checkboxes, so I guess there 
>> are two possible ways (perhaps there's another way?):
>> 
>> 1) disable the control (i.e. gray out) so that the user cannot toggle it (in 
>> one single method)
> 
> There is no checkbox control. The tableview uses one checkbox cell to
> draw the entire column. So you can't just selectively disable checkbox
> instances because there is only one checkbox.
> 
> Disable the cell in -tableView:willDisplayCell:forTableColumn:row:.
> Alternatively, if you're using bindings, bind the table column's
> "enabled" binding to a key that returns YES or NO as appropriate.
> 
> --Kyle Sluder

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: problem bringing up print dialog for epson printer in 64-bit mode

2011-05-21 Thread Ken Victor 
nick,
thanx for the reply.

here is a copy of the top portion of the stack trace for the first exception:

#0  0x7fff839570da in objc_exception_throw
#1  0x12d71431f in +[CERPException(ExceptionMethod) 
debugThrow:function:file:line:]
#2  0x12d76b3d0 in -[CERPCFBundle(InitializeCleanupMethod) 
onInitializeWithIdentifier:]
#3  0x12d78815d in -[CERPCFModuleHandler(InitializeModuleMethod) 
initializeModule]
#4  0x12d7743f0 in -[CERPEPIJDataManager(EventHandlerMethod) onInitialize:]
#5  0x12d716ed3 in -[CERPPDEDataManager(EventHandlerMethod) onInitialize:]
#6  0x12d772d4c in -[CERPCocoaPDESystem(SystemInitializeMethod) 
initializeSystem]
#7  0x12d7728ae in -[CERPCocoaPDESystem(EventHandlerMethod) 
onCocoaPDEPDEPanelsForType:]
#8  0x12d7725a7 in -[CERPCocoaPDESystem(EventHandlerMethod) 
onSystemMessage:data:param:]
#9  0x12d72ae1b in +[CERPSystemInterface(SendSystemMessageMethod) 
sendMessageToSystem:data:param:]
#10 0x12d72ac27 in -[CERPPDEInterface(PDEPlugInOverrideMethod) 
PDEPanelsForType:withHostInfo:]
#11 0x103bb683a in return_buffer.16727
#12 0x103bb6531 in return_buffer.16727
#13 0x103bb4dbf in return_buffer.16727
#14 0x103bc68ca in RunningAsRoot
#15 0x103bc61a6 in RunningAsRoot
#16 0x7fff85cb65b5 in -[NSWindowController _windowDidLoad]
#17 0x7fff85c53d6f in -[NSWindowController window]
#18 0x7fff860d87b6 in -[NSPrintPanel 
beginSheetWithPrintInfo:modalForWindow:delegate:didEndSelector:contextInfo:]
#19 0x1000ad1ac in -[KVWindow printWindow:] at KVWindow.mm:385

and here is the second exception:

#0  0x7fff839570da in objc_exception_throw
#1  0x7fff870a2110 in -[NSObject(NSObject) doesNotRecognizeSelector:]
#2  0x7fff8701a91f in ___forwarding___
#3  0x7fff87016a68 in __forwarding_prep_0___
#4  0x7fff86779a2c in NSExceptionHandlerExceptionRaiser
#5  0x7fff839570f3 in objc_exception_throw
#6  0x12d71431f in +[CERPException(ExceptionMethod) 
debugThrow:function:file:line:]
#7  0x12d76b3d0 in -[CERPCFBundle(InitializeCleanupMethod) 
onInitializeWithIdentifier:]
#8  0x12d78815d in -[CERPCFModuleHandler(InitializeModuleMethod) 
initializeModule]
#9  0x12d7743f0 in -[CERPEPIJDataManager(EventHandlerMethod) onInitialize:]
#10 0x12d716ed3 in -[CERPPDEDataManager(EventHandlerMethod) onInitialize:]
#11 0x12d772d4c in -[CERPCocoaPDESystem(SystemInitializeMethod) 
initializeSystem]
#12 0x12d7728ae in -[CERPCocoaPDESystem(EventHandlerMethod) 
onCocoaPDEPDEPanelsForType:]
#13 0x12d7725a7 in -[CERPCocoaPDESystem(EventHandlerMethod) 
onSystemMessage:data:param:]
#14 0x12d72ae1b in +[CERPSystemInterface(SendSystemMessageMethod) 
sendMessageToSystem:data:param:]
#15 0x12d72ac27 in -[CERPPDEInterface(PDEPlugInOverrideMethod) 
PDEPanelsForType:withHostInfo:]
#16 0x103bb683a in return_buffer.16727
#17 0x103bb6531 in return_buffer.16727
#18 0x103bb4dbf in return_buffer.16727
#19 0x103bc68ca in RunningAsRoot
#20 0x103bc61a6 in RunningAsRoot
#21 0x7fff85cb65b5 in -[NSWindowController _windowDidLoad]
#22 0x7fff85c53d6f in -[NSWindowController window]
#23 0x7fff860d87b6 in -[NSPrintPanel 
beginSheetWithPrintInfo:modalForWindow:delegate:didEndSelector:contextInfo:]
#24 0x1000ad1ac in -[KVWindow printWindow:] at KVWindow.mm:385

i won’t bother with the other 8 exceptions as i don’t think they can help find 
the problem, but if any one would like me to post the stack traces for all 10 
exceptions, i can.

thanx for any suggestions you may be able to provide,
ken



On May 20, 2011, at 10:40 PM, Nick Zitzmann wrote:

> 
> On May 20, 2011, at 4:41 PM, Ken Victor wrote:
> 
>> the following problem only occurs when i run my app in 64-bit mode; i.e., it 
>> does not happen when i run in 32-bit mode. my environment is snow leopard 
>> 10.6.7 running on a mac pro.
>> 
>> when i call:
>>  -[NSPrintPanel 
>> beginSheetWithPrintInfo:modalForWindow:delegate:didEndSelector:contextInfo:]
>> 
>> i get the following (either in the console log or the xcode console when i 
>> run under xcode):
>> 
>> 5/19/11 4:14:49 PM   Accounts[18320] -[NSError 
>> _addExceptionHandlerStackTrace]: unrecognized selector sent to instance 
>> 0x126795280
> [...]
>> can anyone offer me a clue/suggestion as to what might be causing this 
>> problem and how i can go about fixing it?
> 
> If you can reproduce the problem locally, have you tried breaking on 
> objc_exception_throw, reproducing the problem, and then looking at the 
> circumstances leading up to the exception?
> 
> Nick Zitzmann
> 
> 
> 
> 

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email

Synthesize getter in a NSThread

2011-05-21 Thread Tony Romano 
I am running into an issue using a synthesized getter in a thread.
Observing memory consumed by the application in Activity Monitor, memory
continues to grow ~200k per sample until the OS gives an Out Of Memory
warning.  If I code my own getter, the app behaves as expected.  I have
striped it down to basically one call as follows:

-(void) process:(LeakyThreadAppDelegate *) myDelegate

{

NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];

// Extract the object that contains the thread object

SomeClass *obj = [myDelegate myClass];

NSLog(@"Thread Starting");

// Simplified to illustrate the problem

while (1) {



if ([[obj thread] isCancelled] == YES) {

break; 

}

}

NSLog(@"Thread Cancelled");

[pool release];

}


Any clues as to what is wrong?  Thanks In Advance.

I have created a complete sample and pushed it up to GitHub:
git://github.com/tonyrom/Leaky-Getter-Sample-Code.git

-tony





___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

where do I find the files of the media templates on my harddisk?

2011-05-21 Thread Martin Batholdy 
Hi,

Does someone know where I can find the original image files of the templates 
you can choose in Interface Builder?

More precisely I look for the original file of 
NSStopProgressFreestandingTemplate.


thanks!

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: where do I find the files of the media templates on my harddisk?

2011-05-21 Thread Kyle Sluder 
On Sat, May 21, 2011 at 4:11 PM, Martin Batholdy
 wrote:
> Hi,
>
> Does someone know where I can find the original image files of the templates 
> you can choose in Interface Builder?

They don't necessarily exist. They're part of the CoreUI framework.

> More precisely I look for the original file of 
> NSStopProgressFreestandingTemplate.

You are not licensed to make modifications to the original artwork, if
that's what you're after.

--Kyle Sluder
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

CVDisplayLink slows down execution of independent NSTimer

2011-05-21 Thread Travis Kirton 
Hi,

I am playing around with CVDisplayLink, I have it set up and running
properly.

I also have another method called update, which I am trying to run using a
timer set to 60.0 frames per second.

When I run the application without starting the CVDisplayLink, the update
function runs very near to 60.0 fps...

BUT, when the displaylink is running, the speed of the update drops to
somewhere between 12 and 14 fps...

I didn't expect such a drop.

Also, I am running this in an NSOpenGLView, and call [self setNeedsDisplay]
every time the displaylink triggers.

Any thoughts on the performance issue?

Cheers,
T
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Synthesize getter in a NSThread

2011-05-21 Thread Ken Thomases 
On May 21, 2011, at 3:27 PM, Tony Romano wrote:

> I am running into an issue using a synthesized getter in a thread.
> Observing memory consumed by the application in Activity Monitor, memory
> continues to grow ~200k per sample until the OS gives an Out Of Memory
> warning.  If I code my own getter, the app behaves as expected.  I have
> striped it down to basically one call as follows:
> 
> -(void) process:(LeakyThreadAppDelegate *) myDelegate
> 
> {
> 
> NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
> 
> // Extract the object that contains the thread object
> 
> SomeClass *obj = [myDelegate myClass];
> 
> NSLog(@"Thread Starting");
> 
> // Simplified to illustrate the problem
> 
> while (1) {
> 
> 
> 
> if ([[obj thread] isCancelled] == YES) {
> 
> break; 
> 
> }
> 
> }
> 
> NSLog(@"Thread Cancelled");
> 
> [pool release];
> 
> }
> 
> 
> Any clues as to what is wrong?  Thanks In Advance.

A synthesized getter is entitled to put objects into the autorelease pool.  The 
above code does not drain the pool until after the thread is cancelled.  
Everything autoreleased before then just accumulates.  Try draining the pool 
each iteration of the loop.

Regards,
Ken

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Synthesize getter in a NSThread

2011-05-21 Thread Tony Romano 
Unless I misread the documentation on drain, adding a [pool drain]will
cause the pool to be deallocated.  I tried it anyways, and I get a couple
of emits in the console.

// This message emits when a call to the getter is made
2011-05-21 20:23:39.515 LeakyThread[5947:5707] ***
__NSAutoreleaseNoPool(): Object 0x10011d720 of class NSCFString
autoreleased with no pool in place - just leaking

// This message emits when a call to pool drain is called.
2011-05-21 20:23:39.515 LeakyThread[5947:5707] *** -[NSAutoreleasePool
drain]: This pool has already been drained, do not release it (double
release).


Still not sure what the problem is.
Tony Romano



On 5/21/11 6:58 PM, "Ken Thomases"  wrote:

>On May 21, 2011, at 3:27 PM, Tony Romano wrote:
>
>> I am running into an issue using a synthesized getter in a thread.
>> Observing memory consumed by the application in Activity Monitor, memory
>> continues to grow ~200k per sample until the OS gives an Out Of Memory
>> warning.  If I code my own getter, the app behaves as expected.  I have
>> striped it down to basically one call as follows:
>> 
>> -(void) process:(LeakyThreadAppDelegate *) myDelegate
>> 
>> {
>> 
>> NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
>> 
>> // Extract the object that contains the thread object
>> 
>> SomeClass *obj = [myDelegate myClass];
>> 
>> NSLog(@"Thread Starting");
>> 
>> // Simplified to illustrate the problem
>> 
>> while (1) {
>> 
>> 
>> 
>> if ([[obj thread] isCancelled] == YES) {
>> 
>> break; 
>> 
>> }
>> 
>> }
>> 
>> NSLog(@"Thread Cancelled");
>> 
>> [pool release];
>> 
>> }
>> 
>> 
>> Any clues as to what is wrong?  Thanks In Advance.
>
>A synthesized getter is entitled to put objects into the autorelease
>pool.  The above code does not drain the pool until after the thread is
>cancelled.  Everything autoreleased before then just accumulates.  Try
>draining the pool each iteration of the loop.
>
>Regards,
>Ken
>
>


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Synthesize getter in a NSThread

2011-05-21 Thread Roland King 
both allocate a new pool AND drain it each iteration of the loop

while( 1 )
{
pool = [ [ NSAutoReleasePool alloc ] init ];

// do stuff

[ pool drain ];
}

On 22-May-2011, at 11:28 AM, Tony Romano wrote:

> Unless I misread the documentation on drain, adding a [pool drain]will
> cause the pool to be deallocated.  I tried it anyways, and I get a couple
> of emits in the console.
> 
> // This message emits when a call to the getter is made
> 2011-05-21 20:23:39.515 LeakyThread[5947:5707] ***
> __NSAutoreleaseNoPool(): Object 0x10011d720 of class NSCFString
> autoreleased with no pool in place - just leaking
> 
> // This message emits when a call to pool drain is called.
> 2011-05-21 20:23:39.515 LeakyThread[5947:5707] *** -[NSAutoreleasePool
> drain]: This pool has already been drained, do not release it (double
> release).
> 
> 
> Still not sure what the problem is.
> Tony Romano
> 
> 
> 
> On 5/21/11 6:58 PM, "Ken Thomases"  wrote:
> 
>> On May 21, 2011, at 3:27 PM, Tony Romano wrote:
>> 
>>> I am running into an issue using a synthesized getter in a thread.
>>> Observing memory consumed by the application in Activity Monitor, memory
>>> continues to grow ~200k per sample until the OS gives an Out Of Memory
>>> warning.  If I code my own getter, the app behaves as expected.  I have
>>> striped it down to basically one call as follows:
>>> 
>>> -(void) process:(LeakyThreadAppDelegate *) myDelegate
>>> 
>>> {
>>> 
>>> NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
>>> 
>>> // Extract the object that contains the thread object
>>> 
>>> SomeClass *obj = [myDelegate myClass];
>>> 
>>> NSLog(@"Thread Starting");
>>> 
>>> // Simplified to illustrate the problem
>>> 
>>> while (1) {
>>> 
>>> 
>>> 
>>> if ([[obj thread] isCancelled] == YES) {
>>> 
>>> break; 
>>> 
>>> }
>>> 
>>> }
>>> 
>>> NSLog(@"Thread Cancelled");
>>> 
>>> [pool release];
>>> 
>>> }
>>> 
>>> 
>>> Any clues as to what is wrong?  Thanks In Advance.
>> 
>> A synthesized getter is entitled to put objects into the autorelease
>> pool.  The above code does not drain the pool until after the thread is
>> cancelled.  Everything autoreleased before then just accumulates.  Try
>> draining the pool each iteration of the loop.
>> 
>> Regards,
>> Ken
>> 
>> 
> 
> 
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org
> 
> This email sent to r...@rols.org

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Synthesize getter in a NSThread

2011-05-21 Thread Tony Romano 
Yes, allocating the pool in the loop in conjunction with the drain did the
trick. It wont be too bad in the actual code because my thread is not free
running with a while(1), I use a condition lock.

Thanks for the help guys.

Tony Romano


On 5/21/11 8:31 PM, "Roland King"  wrote:

>both allocate a new pool AND drain it each iteration of the loop
>
>while( 1 )
>{
>pool = [ [ NSAutoReleasePool alloc ] init ];
>
>// do stuff
>
>[ pool drain ];
>}
>
>On 22-May-2011, at 11:28 AM, Tony Romano wrote:
>
>> Unless I misread the documentation on drain, adding a [pool drain]will
>> cause the pool to be deallocated.  I tried it anyways, and I get a
>>couple
>> of emits in the console.
>> 
>> // This message emits when a call to the getter is made
>> 2011-05-21 20:23:39.515 LeakyThread[5947:5707] ***
>> __NSAutoreleaseNoPool(): Object 0x10011d720 of class NSCFString
>> autoreleased with no pool in place - just leaking
>> 
>> // This message emits when a call to pool drain is called.
>> 2011-05-21 20:23:39.515 LeakyThread[5947:5707] *** -[NSAutoreleasePool
>> drain]: This pool has already been drained, do not release it (double
>> release).
>> 
>> 
>> Still not sure what the problem is.
>> Tony Romano
>> 
>> 
>> 
>> On 5/21/11 6:58 PM, "Ken Thomases"  wrote:
>> 
>>> On May 21, 2011, at 3:27 PM, Tony Romano wrote:
>>> 
 I am running into an issue using a synthesized getter in a thread.
 Observing memory consumed by the application in Activity Monitor,
memory
 continues to grow ~200k per sample until the OS gives an Out Of Memory
 warning.  If I code my own getter, the app behaves as expected.  I
have
 striped it down to basically one call as follows:
 
 -(void) process:(LeakyThreadAppDelegate *) myDelegate
 
 {
 
 NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
 
 // Extract the object that contains the thread object
 
 SomeClass *obj = [myDelegate myClass];
 
 NSLog(@"Thread Starting");
 
 // Simplified to illustrate the problem
 
 while (1) {
 
 
 
 if ([[obj thread] isCancelled] == YES) {
 
 break; 
 
 }
 
 }
 
 NSLog(@"Thread Cancelled");
 
 [pool release];
 
 }
 
 
 Any clues as to what is wrong?  Thanks In Advance.
>>> 
>>> A synthesized getter is entitled to put objects into the autorelease
>>> pool.  The above code does not drain the pool until after the thread is
>>> cancelled.  Everything autoreleased before then just accumulates.  Try
>>> draining the pool each iteration of the loop.
>>> 
>>> Regards,
>>> Ken
>>> 
>>> 
>> 
>> 
>> ___
>> 
>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>> 
>> Please do not post admin requests or moderator comments to the list.
>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>> 
>> Help/Unsubscribe/Update your Subscription:
>> http://lists.apple.com/mailman/options/cocoa-dev/rols%40rols.org
>> 
>> This email sent to r...@rols.org
>
>


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Moderator - Re: Looking for iPhone App developers

2011-05-21 Thread Scott Anguish 
Reminder:

All job offers are to be passed by the moderators first (address is listed in 
every message)

Not all are approved, but most are.

This is to prevent this from becoming a list of people just looking for 
engineers rather that the purpose of discussing cocoa development.


On May 19, 2011, at 4:20 AM, Ellen Chou wrote:

> I'm looking for an experienced iPhone developer for 6 months.
> 
> Location - San Jose, CA
> 
> Recruiters are not welcomed.
> 
> Please reply if you are interested.
> 
> Thanks.
> Ellen
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/scott%40cocoadoc.com
> 
> This email sent to sc...@cocoadoc.com

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com