Weird UITableView behavior after scrolling and inserting new row?

"YOU AND THE ART OF ONLINE DATING" is the only product on the market that will take you step-by-step through the process of online dating, provide you with the resources to help ensure success. Get it now!

I had some similar experiences with the Simulator recently - I'm dealing with an application driving several table views from Core Data, and it also presents a bunch of UIAlertViews and UIActionSheets at various points through the application I've noticed that the Simulator doesn't respond well to touch events right after a UI action (table cell insert, action sheet display, etc. ) occurs. It usually helps for me to either switch to another window then back to the Simulator or click and drag the mouse through some touch-inactive area of the Simulator, then try the action I want again Your mileage may URL1 may be a pain during testing, but as long as everything works properly on the device, you should be fine.

I had some similar experiences with the Simulator recently - I'm dealing with an application driving several table views from Core Data, and it also presents a bunch of UIAlertViews and UIActionSheets at various points through the application. I've noticed that the Simulator doesn't respond well to touch events right after a UI action (table cell insert, action sheet display, etc. ) occurs.It usually helps for me to either switch to another window then back to the Simulator or click and drag the mouse through some touch-inactive area of the Simulator, then try the action I want again Your mileage may vary. It may be a pain during testing, but as long as everything works properly on the device, you should be fine.

Your two suggestions didn't work for me, but it is definitely a bug in the simulator. Even reloading the table view won't help! Anyways, thanks for sharing your experience.

– Daniel Rinser Jul 13 '09 at 12:42 Anytime. You may want to file a bug report: bugreport.apple. Com – Tim Jul 13 '09 at 15:41.

Users can add a new customer, thus I have to add a new row to the table view (by updating the data model and calling insertRowsAtIndexPaths:withRowAnimation:). However, since the table view is sorted, this insert can occur off-screen, which is not very nice wrt. This code actually works as expected: The table view scrolls and the new row is inserted correctly.

However, after the insert some table view cells become "irresponsive", ie. They won't display the delete button upon swipe and don't even highlight when selected. Since this is really weird and kinda hard to explain, let me try to illustrate it.

Now, after the insert rows 1 - 5 will not respond to user interaction as described above. Anybody ever experienced this kind of problem? Are there other approaches to make sure that the insertion of new rows is visible for the user?

Update: Just tested on the device, and it turns out that this problem only occurs on the simulator! This makes the issue less unpleasant, but I'd still be interested if someone else has experienced this behavior.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions