Re: While running our iPhone app, the screen sometimes goes white and locks up. Any idea why?

2012-01-23 Thread G S
Good info. Thanks, guys!
___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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


Changing Album Name property of the audio book track, does not affect the title of Audiobook on iOS5 device.

2012-01-23 Thread Payal Mundhada
Hi All,

I am transferring audiobook from Mac OS X to iOS device using iTunes (during 
transfer the audiobook is not copied to iTunes). For the transfer I am using 
apple script (with Cocoa).

I found that if the album name of audiobook is not set, after transfer on iOS 
device (iPhone, iPad..)the audio book is found to be under the title Unknown  
in 'Audiobooks' section .

Before iOS5 i used to set the Album Name property of the tracks on the device  
to the Audiobook title using apple script.  On non iOS5 devices, value for  
album name property of the track is set as  title for Audiobook on device. But 
for iOS 5 device though the Album Name property is set successfully, the tracks 
are still with the title Unknown.

Then I tried, copy the audiobook to iTunes, set the Album Name property of 
tracks and then copied these audiobook tracks to the iOS5 device. This time I 
noticed that the title for same Audiobook was set which was Unknown last time 
( when copied the tracks directly to device and then changed the Album Name).

Is it like that changing the Album Name property of track on device does not 
affect?

It would be grate to find any help regarding setting title of audiobook on iOS5 
device from Unknown to desired value.

Thanks

DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Ltd. does not accept any liability for virus infected mails.
___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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


Re: NSOpenPanel problem

2012-01-23 Thread Jan E. Schotsman


On Jan 23, 2012, at 5:17 AM, Ken Thomases wrote:


On Jan 22, 2012, at 1:24 PM, Jan E. Schotsman wrote:

Suppose I want to display a modeless choose file dialog with the  
beginWithCompletionHandler method.

How can I pass some context info to the handler?


Blocks capture whatever local variables you reference within them.   
If you reference instance variables, they capture self and then  
access the ivars from that.  Just use whatever value you want,  
directly.  That's the great thing about blocks.


That's great indeed, but I need the block to work with a method  
parameter (an NSString object). Do I need to copy the NSString to an  
ivar?


-method:(NSString *)someString
{
(void)(^handler)(NSInteger result)  =   { uses someString  };

[openPanel beginWithCompletionHandler: handler];
}

I have a related question for the old beginForDirectory method:

if I try to pass on someString in a C struct (contextInfo) then the  
compiler complains that ARC doesn't like object pointers in C structs.

I could serialize and unserialize the string. Or is there a better way?

Jan E.

___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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


Re: NSOpenPanel problem

2012-01-23 Thread Conrad Shultz
(Re-post on list.)

On 1/23/12 1:41 AM, Jan E. Schotsman wrote:
 That's great indeed, but I need the block to work with a method
 parameter (an NSString object). Do I need to copy the NSString to an ivar?

No, you just use it directly.  As Ken mentioned, any variable you
reference in a block is automatically captured by the block and remains
available for the duration of its existence - even outside the scope of
the original variable declaration.

(If you need to *write* to an outside variable inside a block, the
variable's declaration must include a __block modifier; this and other
quirks are noted in the documentation.)

You *really* need to read the docs on blocks and GCD since they are the
modern way of writing threaded code, implementing callbacks, etc.  I'd
start with the Short Practical Guide to Blocks -
http://developer.apple.com/library/ios/#featuredarticles/Short_Practical_Guide_Blocks/_index.html.

There are a plethora of WWDC videos from beginning to advanced on these
topics, too.

 if I try to pass on someString in a C struct (contextInfo) then the
 compiler complains that ARC doesn't like object pointers in C structs.
 I could serialize and unserialize the string. Or is there a better way?

Just use the NSString * right in the block - no need for structs,
serialization, or anything.  That's why blocks are so useful.

-- 
Conrad Shultz

Synthetiq Solutions
www.synthetiqsolutions.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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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


Re: Cocoa-dev Digest, Vol 9, Issue 39

2012-01-23 Thread lpeng...@gmail.com
Re: Versions, -windowWillClose: (Martin Hewitson)
  2. Re: NSSlider and arrangedObjects (Ken Thomases)
  3. Re: NSXMLParser, streams, multiple threads, and crashing
 (Jens Alfke)
  4. Re: NSXMLParser, streams, multiple threads, and crashing
 (Thomas Davie)
  5. Re: NSTextView : Scroll top when bound-to string changes
 (Ken Thomases)
  6. Re: While running our iPhone app,the screen sometimes goes
 white and locks up. Any idea why? (Greg Parker)
  7. NSOpenPanel problem (Jan E. Schotsman)
  8. Re: NSOpenPanel problem (Ken Thomases)
  9. Re: Cocoa-dev Digest, Vol 9, Issue 38 (lpeng...@gmail.com)
 10. Re: While running our iPhone app,the screen sometimes goes
 white and locks up. Any idea why? (G S)
 11. Changing Album Name property of the audio book track,does

Jim Lin

在 2012-1-23,17:18,cocoa-dev-requ...@lists.apple.com 写道:

 Re: Versions, -windowWillClose: (Martin Hewitson)
   2. Re: NSSlider and arrangedObjects (Ken Thomases)
   3. Re: NSXMLParser, streams, multiple threads, and crashing
  (Jens Alfke)
   4. Re: NSXMLParser, streams, multiple threads, and crashing
  (Thomas Davie)
   5. Re: NSTextView : Scroll top when bound-to string changes
  (Ken Thomases)
   6. Re: While running our iPhone app,the screen sometimes goes
  white and locks up. Any idea why? (Greg Parker)
   7. NSOpenPanel problem (Jan E. Schotsman)
   8. Re: NSOpenPanel problem (Ken Thomases)
   9. Re: Cocoa-dev Digest, Vol 9, Issue 38 (lpeng...@gmail.com)
  10. Re: While running our iPhone app,the screen sometimes goes
  white and locks up. Any idea why? (G S)
  11. Changing Album Name property of the audio book track,does
___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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

Re: NSOpenPanel problem

2012-01-23 Thread Jan E. Schotsman


On Jan 23, 2012, at 11:37 AM, Conrad Shultz wrote:

You *really* need to read the docs on blocks and GCD since they are  
the
modern way of writing threaded code, implementing callbacks, etc.   
I'd

start with the Short Practical Guide to Blocks -
http://developer.apple.com/library/ios/#featuredarticles/ 
Short_Practical_Guide_Blocks/_index.html.



OK, will do that.


if I try to pass on someString in a C struct (contextInfo) then the
compiler complains that ARC doesn't like object pointers in C  
structs.
I could serialize and unserialize the string. Or is there a better  
way?


Just use the NSString * right in the block - no need for structs,
serialization, or anything.  That's why blocks are so useful.



I still need an alternative because I want to support Leopard where  
blocks aren't available. I've written some code using  
NSPropertyListSerialization which should do the trick.


Jan E.

___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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


Re: NSOpenPanel problem

2012-01-23 Thread Ken Thomases
On Jan 23, 2012, at 9:16 AM, Jan E. Schotsman wrote:

 On Jan 23, 2012, at 11:37 AM, Conrad Shultz wrote:
 
 if I try to pass on someString in a C struct (contextInfo) then the
 compiler complains that ARC doesn't like object pointers in C structs.
 I could serialize and unserialize the string. Or is there a better way?
 
 Just use the NSString * right in the block - no need for structs,
 serialization, or anything.  That's why blocks are so useful.
 
 
 I still need an alternative because I want to support Leopard where blocks 
 aren't available. I've written some code using NSPropertyListSerialization 
 which should do the trick.

If you're supporting Leopard, then you can't use ARC and the original problem 
goes away.  Also, serializing a string doesn't help because you still have a 
Cocoa object -- an NSData now instead of an NSString -- and you have to manage 
its memory just the same.

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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


Re: NSOpenPanel problem

2012-01-23 Thread Jan E. Schotsman


On Jan 23, 2012, at 5:08 PM, Ken Thomases wrote:

If you're supporting Leopard, then you can't use ARC and the  
original problem goes away.


??? I have set development target = 10.7 SDK,  deployment target =  
10.5 and ARC is on.
The compiler doesn't complain. I have clicked the validate settings  
button and no problems are reported. Latest Mac OS, latest Xcode.


Also, serializing a string doesn't help because you still have a  
Cocoa object -- an NSData now instead of an NSString -- and you have  
to manage its memory just the same.


That's what [data getBytes:length:] is for.

Jan E.
___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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


What causes a UITableViewCell to be deallocated?

2012-01-23 Thread Laurent Daudelin
Hello.

I'm trying to track a crash in our app where we have a custom UITableView cell 
that contains a UITextView because we need the ability to display and open 
links that might be in the text we're displaying in the text view.

The problem is that somehow, the cell is deallocated and WebKit complains that 
it's been unable to obtain the web lock from a thread other than the main 
thread or the web thread when it's deallocated. I have reviewed the code and 
checked all the reload… message we might send to the table view that could 
cause the deallocation of its cells but all of those calls are executed from 
the main thread using [[NSOperationQueue mainQueue] addOperationWithBlock:^{…}] 
so I'm stumped. Are there any other situations where UITableView cells would be 
deallocated? The view displays and the view isn't unloaded due to memory 
warning or any other situation.

-Laurent.
-- 
Laurent Daudelin
AIM/iChat/Skype:LaurentDaudelin 
http://www.nemesys-soft.com/
Logiciels Nemesys Software  
laur...@nemesys-soft.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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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

vForce Performance

2012-01-23 Thread dct
I recently posted a query on the Xcode-Users list but with no reply so far.

I hopes of accelerating some standard C functions, I've run a few timing 
experiments to assess vForce.h function performance.  The results are 
disappointing.

 - Comparing the time to run vvsqrt( ) on a 1 point data file to a simple 
for( ) loop,
   i.e., for( ii=0; ii1; ii++ ) yy[ii] = sqrt[ii] , shows a very slight 
improvement 
( ~23 nsec per input data pt. for vvsqrt vice ~24 nsec for the loop),
 - Comparing the time to run vvsin( ) in similar fashion actually shows the 
loop to be better--
 ( ~39 nsec per data pt. for vvsin vice ~21 nsec for the loop).

(FYI,  tests were run under Xcode 3.2.3 on a MacPro w Dual-Core, 3 GHz Xeon 
processor.)

My questions are:
  - Are these timing results consistent with expected vForce performance?
 - If not, what does one need to do to get the expected performance?
 - And, regardless, are there other considerations that would favor use of the 
vForce functions?

Don Thompson
___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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


Re: NSOpenPanel problem

2012-01-23 Thread Ken Thomases
On Jan 23, 2012, at 12:22 PM, Jan E. Schotsman wrote:

 On Jan 23, 2012, at 5:08 PM, Ken Thomases wrote:
 
 If you're supporting Leopard, then you can't use ARC and the original 
 problem goes away.
 
 ??? I have set development target = 10.7 SDK,  deployment target = 10.5 and 
 ARC is on.
 The compiler doesn't complain. I have clicked the validate settings button 
 and no problems are reported. Latest Mac OS, latest Xcode.

I don't know about complaints from the compiler, but I'm certain that ARC can't 
be used with code deployed to Leopard.  ARC requires support from the runtime 
libraries and that support was never released for Leopard.

For example, the Transitioning to ARC Release Notes say, ARC is supported in 
Xcode 4.2 for Mac OS X v10.6 and v10.7 (64-bit applications).
http://developer.apple.com/library/mac/#releasenotes/ObjectiveC/RN-TransitioningToARC/_index.html


 Also, serializing a string doesn't help because you still have a Cocoa 
 object -- an NSData now instead of an NSString -- and you have to manage its 
 memory just the same.
 
 That's what [data getBytes:length:] is for.

I can't imagine that allocating a heap buffer for a serialized string is the 
best way to get data into the handler.  If you are using ARC (which I believe 
you can't), then try CFBridgingRetain() balanced later with a CFRelease() or 
CFBridgingRelease().

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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


Re: What causes a UITableViewCell to be deallocated?

2012-01-23 Thread Luke Hiesterman
Think about it simply. A cell gets deallocated just like any other object - 
when its retain count goes to zero. If you're looking for a cell getting 
deallocated on a non-main thread, you're looking for a place release is being 
called on a non-main thread. I would think you could just override the dealloc 
method to help you track this situation in the debugger. Perhaps add an 
NSAssert([NSThread isMainThread], @wups); in there.

Luke

On Jan 23, 2012, at 11:38 AM, Laurent Daudelin wrote:

 Hello.
 
 I'm trying to track a crash in our app where we have a custom UITableView 
 cell that contains a UITextView because we need the ability to display and 
 open links that might be in the text we're displaying in the text view.
 
 The problem is that somehow, the cell is deallocated and WebKit complains 
 that it's been unable to obtain the web lock from a thread other than the 
 main thread or the web thread when it's deallocated. I have reviewed the code 
 and checked all the reload… message we might send to the table view that 
 could cause the deallocation of its cells but all of those calls are executed 
 from the main thread using [[NSOperationQueue mainQueue] 
 addOperationWithBlock:^{…}] so I'm stumped. Are there any other situations 
 where UITableView cells would be deallocated? The view displays and the view 
 isn't unloaded due to memory warning or any other situation.
 
 -Laurent.
 -- 
 Laurent Daudelin
 AIM/iChat/Skype:LaurentDaudelin   
 http://www.nemesys-soft.com/
 Logiciels Nemesys Software
 laur...@nemesys-soft.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:
 https://lists.apple.com/mailman/options/cocoa-dev/luketheh%40apple.com
 
 This email sent to luket...@apple.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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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

Re: What causes a UITableViewCell to be deallocated?

2012-01-23 Thread Laurent Daudelin
It seems that the deallocation happens when a block is being deallocated. Is it 
possible that a block ran on the main queue of an NSOperationQueue could be 
deallocated in another thread?

-Laurent.
-- 
Laurent Daudelin
AIM/iChat/Skype:LaurentDaudelin 
http://www.nemesys-soft.com/
Logiciels Nemesys Software  
laur...@nemesys-soft.com

On Jan 23, 2012, at 13:49, Laurent Daudelin wrote:

 Hello Luke.
 
 Well, I already checked that. The cell is being deallocated from a secondary 
 thread but there is nothing in the thread that indicates what triggered it. 
 It looks like a performSelector:withObject:afterDelay: or something like it 
 but we don't have any of those in the table view controller that controls the 
 table view. Like I said in my original message, I've looked for any flavor of 
 UITableView reload… and the only calls we have are reloadData but they are 
 all executed on the main thread using [[NSOperationQueue] mainQueue] 
 addOperationWithBlock: so I'm stumped as to where this deallocation is 
 triggered. I've checked all the other running threads and I can't find any 
 code that you reload the table view which could cause its cells to be 
 deallocated.
 
 -Laurent.
 -- 
 Laurent Daudelin
 AIM/iChat/Skype:LaurentDaudelin   
 http://www.nemesys-soft.com/
 Logiciels Nemesys Software
 laur...@nemesys-soft.com
 
 On Jan 23, 2012, at 13:38, Luke Hiesterman wrote:
 
 Think about it simply. A cell gets deallocated just like any other object - 
 when its retain count goes to zero. If you're looking for a cell getting 
 deallocated on a non-main thread, you're looking for a place release is 
 being called on a non-main thread. I would think you could just override the 
 dealloc method to help you track this situation in the debugger. Perhaps add 
 an NSAssert([NSThread isMainThread], @wups); in there.
 
 Luke
 
 On Jan 23, 2012, at 11:38 AM, Laurent Daudelin wrote:
 
 Hello.
 
 I'm trying to track a crash in our app where we have a custom UITableView 
 cell that contains a UITextView because we need the ability to display and 
 open links that might be in the text we're displaying in the text view.
 
 The problem is that somehow, the cell is deallocated and WebKit complains 
 that it's been unable to obtain the web lock from a thread other than the 
 main thread or the web thread when it's deallocated. I have reviewed the 
 code and checked all the reload… message we might send to the table view 
 that could cause the deallocation of its cells but all of those calls are 
 executed from the main thread using [[NSOperationQueue mainQueue] 
 addOperationWithBlock:^{…}] so I'm stumped. Are there any other situations 
 where UITableView cells would be deallocated? The view displays and the 
 view isn't unloaded due to memory warning or any other situation.
 
 -Laurent.
 -- 
 Laurent Daudelin
 AIM/iChat/Skype:LaurentDaudelin 
 http://www.nemesys-soft.com/
 Logiciels Nemesys Software  
 laur...@nemesys-soft.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:
 https://lists.apple.com/mailman/options/cocoa-dev/luketheh%40apple.com
 
 This email sent to luket...@apple.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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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

Re: What causes a UITableViewCell to be deallocated?

2012-01-23 Thread Steve Christensen
A UITableViewCell could be deallocated as soon as its row scrolls out of view. 
UITableView will reuse cells if you specify a reuse identifier, but I don't 
believe that the docs actually specify the number of cells that are reused.

I'm assuming that the web view is displayed when the user taps a link in the 
UITextView. If so, when does the crash occur relative to the appearance of the 
web view?


On Jan 23, 2012, at 11:38 AM, Laurent Daudelin wrote:

 I'm trying to track a crash in our app where we have a custom UITableView 
 cell that contains a UITextView because we need the ability to display and 
 open links that might be in the text we're displaying in the text view.
 
 The problem is that somehow, the cell is deallocated and WebKit complains 
 that it's been unable to obtain the web lock from a thread other than the 
 main thread or the web thread when it's deallocated. I have reviewed the code 
 and checked all the reload… message we might send to the table view that 
 could cause the deallocation of its cells but all of those calls are executed 
 from the main thread using [[NSOperationQueue mainQueue] 
 addOperationWithBlock:^{…}] so I'm stumped. Are there any other situations 
 where UITableView cells would be deallocated? The view displays and the view 
 isn't unloaded due to memory warning or any other situation.


___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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

Re: What causes a UITableViewCell to be deallocated?

2012-01-23 Thread Laurent Daudelin
Steve,

There are no web views. Because we're using a UITextView, it loads the WebKit 
behind the scene (I guess to support links that could appear in the text in the 
UITextView) and when that UITextView is deallocated from another thread than 
the main thread or the webkit thread, it raises an exception that crashes the 
app. This happens only in iOS 4.3.5. I'm not sure if all my UITableView 
operations are run on the main thread why when that block is deallocated, it 
would be on a secondary thread. That seems to be the problem.

-Laurent.
-- 
Laurent Daudelin
AIM/iChat/Skype:LaurentDaudelin 
http://www.nemesys-soft.com/
Logiciels Nemesys Software  
laur...@nemesys-soft.com

On Jan 23, 2012, at 15:49, Steve Christensen wrote:

 A UITableViewCell could be deallocated as soon as its row scrolls out of 
 view. UITableView will reuse cells if you specify a reuse identifier, but I 
 don't believe that the docs actually specify the number of cells that are 
 reused.
 
 I'm assuming that the web view is displayed when the user taps a link in the 
 UITextView. If so, when does the crash occur relative to the appearance of 
 the web view?
 
 
 On Jan 23, 2012, at 11:38 AM, Laurent Daudelin wrote:
 
 I'm trying to track a crash in our app where we have a custom UITableView 
 cell that contains a UITextView because we need the ability to display and 
 open links that might be in the text we're displaying in the text view.
 
 The problem is that somehow, the cell is deallocated and WebKit complains 
 that it's been unable to obtain the web lock from a thread other than the 
 main thread or the web thread when it's deallocated. I have reviewed the 
 code and checked all the reload… message we might send to the table view 
 that could cause the deallocation of its cells but all of those calls are 
 executed from the main thread using [[NSOperationQueue mainQueue] 
 addOperationWithBlock:^{…}] so I'm stumped. Are there any other situations 
 where UITableView cells would be deallocated? The view displays and the view 
 isn't unloaded due to memory warning or any other situation.
 


___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

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