+10000

https://gist.github.com/e156c472c8664e7a9178

https://gist.github.com/988042808e49fe9646fd

I had the same problem and found the solution - don't use UIImagePNGRepresentation when converting image to NSData. Here the sample how you have to do to have NSData size the same as your image file

NSString path=[[NSBundle mainBundle] pathForResource:@"foto14" ofType:@"jpg"]; NSData imageData = [NSData dataWithContentsOfFile:path];

Ask Different answer http://apple.stackexchange.com/a/49663/8546 focuses on OS X-managed connections to SharePoint, where the file system type is:

* webdav

Other answers to that question focus on other file system types that may be used with WebDAV connections to SharePoint:

* osxfusefs
* transmitdiskfs

Ask Different question http://apple.stackexchange.com/q/14980/8546 focuses on ._ dot underscore files. Answer http://apple.stackexchange.com/a/51147/8546 gives examples of SharePoint interactions with NeoOffice and Microsoft Office. I plan to add an answer to the question of avoidance.

Stack Overflow answer http://stackoverflow.com/a/10561129/38108 is closely aligned with this rdar://8614331

Underlying problem, thanks to Jonukas for the link:

Information about the characters that you cannot use in sites, folders, and files in SharePoint

> … cannot start a file name with the period character. …

I may be losing my mind :) Now the images are showing up fine in Preview. May have jumped to conclusions. Investigating.

The attached images are from TunesWindow's resources:

flat_top_left.png flat_top_middle.png flat_top_right.png

TunesWindow can be downloaded here, for reference:

http://mattgemmell.com/source/

Engineering has determined that this issue behaves as intended based on the following information:

Turn off "Settings > Mail, Contacts, Calendar > Load Remote Images" (which actually applies to all remote contents -- OSX Mail also only refers to "Images" for "any content").

sample: https://www.dropbox.com/s/5dvktl17x0jjtip/videocrash.zip

This no longer crashes (and is 'correctly' spoken) on 10.7.4.

Totally agree

Totally agree

Engineering has determined that this issue behaves as intended based on the following information:

This behavior is actually expected. What is being set is the content inset and this is compensated by the content offset so that the top of the scroll view content can actually be seen when it is first pushed onto the navigation controller. The test for this is fairly simple as you observed in your work around. This behavior was provided mostly for UITableView but since UITableView is a UIScrollView it was generalized a bit.

You should be able to scroll under the navigation bar and the status bar if you set the contentSize of the scrollview to something greater than or equal to the height of the screen. Then you set the contentOffset to (0,0).

I can reproduce it as well. Would be nice, if it's gone.

try to use

#pragma mark

#pragma mark -

#pragma mark - some text

I filed another bug report in rdar://11402376

I'm using Core Data with an entity with an ordered relationship to another entity.

Core Data is generating the signature, "- removeAtIndexes:" in the header file. Yet when I attempt to invoke the method it states, unrecognized selector. Core Data should not generate the declaration if it doesn't provide an implementation. If this is somehow intended to be useful to the developer, the declaration should at least be flagged to indicate its not implemented. Otherwise it is difficult to determine from the generated header what methods are valid and which are not.

Thanks for mentioning this lazyweb and thanks for pointing out the name Steve