I’m not sure if this is related or not but this is the only item that I have
seen (albeit on iOS) where the UI simply would not update on the main thread
and it only happened on an iPad.
This was issuing a makeFirstResponded to a UITextField to display a keyboard.
The keyboard display simply didn’t happen.
There was no lock on the main thread (that I was aware of), it worked fine on
the iPhone, as an iPad in the Simulator just never on the real device.
Then something happened that made me put down the device (frustration), I left
and when I came back, the keyboard was displayed.
Though I never discovered the exact reason why this would happen, it only
happened when the app was run directly from Xcode.
After about 20 seconds, the keyboard would finally display on the device.
Others reported the issue as well. It ended up being something we never needed
to fix since it only happened as an artifact of running the app directly from
Xcode.
Constantly being in a rush, I had never waited to see if the keyboard
eventually displayed or not.
I’m sorry that I don’t have time to review your original code, but what happens
if you try these options:
- issue the update, go off and get a cup of coffee and see if it has updated
when you return.
- if it has not, click the View Hierarchy Debugger
https://i.stack.imgur.com/ezjY4.png or
enter the view debugger method to see if your view is present in the
hierarchy
[myAwesomeView recursiveDescription];
- on an async GCD dispatch, issue a call to a method that…
- updates the attributed string with placeholder text of “XXXXXXXX”
- outputs the contents of the textView to verify that it is your string.
I’m not clear about your super attributed string, but if you are at the point
where you know the proper attributed string is in your textView can you set the
view so that it needs to be updated?
It would be interesting to see if the nasty 20 second view update has reared
its ugly head again.
GL.
Alex Zavatone
_______________________________________________
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
