iOS. UITableView -scrollToRowAtIndexPath blank content - uitableview

I have a question regarding scrollToRowAtIndexPath. It works ok, but sometimes, it shows a blank content until the selected row get's to the top of the tableView. I read somewhere that it has something to do with the fact that the animation is running on main-thread. Any idea how can I solve this issue ? As you can see, the same problem, without any solution Thanks !

Related

Alternative to UITableView.Begin/EndUpdates

We have a custom MonoTouch Dialog (MT D) Element that we want to expand as we type into it.
We experienced the common MT D issue of the height not recalculating. The common solution for that is to call
this.GetContainerTableView().BeginUpdates();
this.GetContainerTableView().EndUpdates();
Stack OverFlow Question
Monotouch: Force UITableView to recalculate height of each cell without reloading data
This has always worked fine for us if even it does smell of HACK. However a user is reporting an issue on their iPhone X that means the whole MT D container (the UITableView) is being scrolled every time which causes the screen to jump.
I have tried temporarily disabling the scroll on the Element's Container and on the immediate RootElement but that made no difference.
Can anyone suggest something to stop the jumping?
I had tried setting scroll position back to it values before Begin and EndUpdates but was getting exceptions trying to hook the scroll event
UIKit.UIApplication.EnsureEventAndDelegateAreNotMismatched
However this suggestion does teh resetting without using Scroll Event. Thanks Kyle Shank
http://www.kyleshank.com/2015/12/05/prevent-uitableview-from-scrolling-during-updates.html
Note:
I spent about a few hours trying to hack my way out of this problem before I posted to SO . In writing the question I found the Kyke Shank solution but decided we'd all be better off if I still wrote up as a question and subsequent answer.

Weird UIStoryBoard Behavior

I am trying to put a UIImageview on top, and two UITextFields follow underneath it. All are confined with Constraints, and it was working fine a few hours ago. But Something weird is happening now. I run the app, and the View comes around but there is no ImageView or where the UITextFields were supposed to be, they aren't visible there anymore, but when i click on that position, the Keyboard pops out, which means there are both UITextFields here but somehow can't be seen. I've cleaned, deleted derived data etc but nothing is coming around. Any idea?
So here are two snapshots that explains that the image "launchSplash" is coming over the other elements. How could I make it go back?
Thank you everyone for helping me out here, it was a mere change or hierarchy of in my Storyboard UI. I didn't put them in the order required and was experiencing this bug. Here are attached snapshots of the new working order of elements in my View Controller.
Thanks again for all your help, Inspecting sure is helpful and fun :)

UITableView Partially Blank in Storyboard

When trying to view a larger UITableView inside of a UIViewController in the storyboard, I can only see/edit the top most cells from the table. The moment I scroll further down the cells are all blank. This is purely for storyboard, the code works fine when running, but any cells in the storyboard that are further down a tableview I can no longer edit since they show as blank.
Here's an example to illustrate
As can be seen from the shift right click, I can't even select the cells that are there.
I know and have experienced problems such as not being able to scroll at all before, such as this, but this is different as I can scroll down but cannot see the rest of the cells of my tableview. Has anyone else ran into this problem, and would know a solution? It seems like it may have something to do with Xcode 7, as I recently upgraded to it.
Although not ideal, I've found a few work arounds for this problem. One solution is to make a temporary UIViewController with a UITableView, and then drag cells into the temp UIViewController until the cell you want to edit is visible. Once you've changed it, drag all the cells in the temporary view controller back into their correct controller. This is extremely hacky, but so far is the only way I've found to visibly see the cell.
Another thing that can be done is that the cells are still editable in the document outline, meaning constraints and elements can still be modified from there. However, it is difficult, as I wasn't able to see the cells being edited, they still appear to be blank.
Hopefully someone else finds/knows of a solution to this and can post it, I'll leave these two workarounds up though they're far from ideal.

Strange animation on inserting and deleting cells in UICollectionView

It seem that inserting and deleting cells in ios6 for UICollectionView works incorrectly. I tried making changes in -finalLayoutAttributesForDisappearingItemAtIndexPath: and initialLayoutAttributesForAppearingItemAtIndexPath: and had no luck in solving the problem. I think the reason it didn't work I don't really get why UICollectionView behaves this way. The video of animation in ios7 is here (it is animation I expect). The way it looks on ios6 can be found here. Please, explain me or give a tip how to get rid of it. Thanks in advance.

Endless scroll issue tumblr, posts at bottom of page "stack"

Here's the issue: tumblr theme that I am using is the NTA 3 column option found on this page (http://themes.ville-noire.com/), which says that I should have 3 columns, infinite scrolling and be able to use a banner. But the earlier posts at the bottom of the page on my blog (http://incandescending.tumblr.com/) do not infinite scroll, and instead kind of stack up, blocking each other.
Do you have any suggestions for why this might be happening and what I can try to fix it? I'm trying to learn and understand a little bit of how coding works but my knowledge/research/attempts haven't done the trick so far- any help appreciated!
Thank you!
It looks like the posts don't have a specific height set so the reason they're 'stacking up' and blocking each other at first is because the height of each post is not defined until they're finished loading.

Resources