Re: iOS AVPlayerViewController and AVPlayer Documentation/Help

Hi Dave, not at all an expert on this but I think if you want “windowed” playback on iOS you need to abandon AVPlayerViewController and instead use your “own” AVPlayer instance pointed at an arbitrary AVPlayerLayer (which some custom view of yours would host). Never done it myself but searching on

iOS AVPlayerViewController and AVPlayer Documentation/Help

Hi, The following code plays a movie file in Full Screen, I’d like to be able to play a Video inside an arbitrary View with the option to go into full screen. I’ve searched for info on this seemingly simple task but can’t seem to find anything useful. I’ve tried setting myPlayerViewController.v

Re: [OT] Question about writing documentation

That’s a cool feature I didn’t know existed! Unfortunately, OGP7.3 crashes when I turn on either instance variables or methods; crash reports submitted. I’ll be looking forward to trying again on the next update. -- Gary L. Wade http://www.garywade.com/ > On Apr 22, 2

Re: [OT] Question about writing documentation

> On 22 Apr 2017, at 18:31, Uli Kusterer wrote: > > On 21. Apr 2017, at 19:28, davel...@mac.com wrote: >> You did't say what you tried, but IMO the best app for professional looking >> figures on the Mac is OmniGraffle from omnigroup.com. There are extensive >> stencil libraries for many thing

Re: [OT] Question about writing documentation

On 21. Apr 2017, at 19:28, davel...@mac.com wrote: > You did't say what you tried, but IMO the best app for professional looking > figures on the Mac is OmniGraffle from omnigroup.com. There are extensive > stencil libraries for many things and I expect one could work (at least as a > starting p

Re: [OT] Question about writing documentation

One of my co-workers made a pretty nice class hierarchy diagram using an open source tool called PlantUML. https://en.wikipedia.org/wiki/PlantUML —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or

Re: [OT] Question about writing documentation

representing Classes/Objecrs. The type of diagrams I’d like are > similar to the ones in the Apple Documentation. > > Thanks in Advance for any suggestions….. > > All the Best > Dave You did't say what you tried, but IMO the best app for professional looking figures on

[OT] Question about writing documentation

Documentation. Thanks in Advance for any suggestions….. All the Best Dave ___ 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

Re: Documentation Workflow

> On Dec 6, 2016, at 3:45 PM, Carl Hoefs wrote: > > Just now I was looking for a list of NSString method signatures to peruse. Open NSString.h? —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moder

Re: Documentation Workflow

ars ago, and then used the “Documents [ >> ] 4293 of 4293” search input to find the doc I was looking for. > > It appears that October 21, 2014 was the last archive date for old style iOS > documentation and content. > > It appears that November 5, 2015 was the l

Re: Documentation Workflow

ooking for. It appears that October 21, 2014 was the last archive date for old style iOS documentation and content. It appears that November 5, 2015 was the last archive date for old style mac documentation and content. This would be a good starting point if you are looking for somethin

Re: Documentation Workflow

> On Dec 2, 2016, at 11:34 AM, Slipp Douglas Thompson > wrote: > > Alternatively, there's always archive.org's Wayback Machine. Very helpful. I did not know this existed. Thanks so much for the example and instructions. --Richard Charles ___ Coc

Re: Documentation Workflow

I bet the documentation has gotten leaner since Apple's developers have been dog-fooding the Xcode feature, Add Documentation, available under the Editor:Structure men path, and only using what’s in there. Just kidding…but maybe not! -- Gary L. Wade http://www.garywade.com/

Re: Documentation Workflow

Alternatively, there's always archive.org's Wayback Machine. For example, the Core Data Programming Guide from 2014-07-03 is available right here: https://web.archive.org/web/20140703032131/https://developer.apple.com/library/ios/documentation/Cocoa/Conceptual/CoreData/cdProgramming

Re: Documentation Workflow

> On 2 Dec 2016, at 23:25, Richard Charles wrote: > > Somebody needs to start an online repository of older Apple developer > documentation in pdf format. I did do exactly that for the legacy AppleScript stuff[1] when it started disappearing, but it’d be a bit of a mammoth ta

Re: Documentation Workflow

> On Nov 12, 2016, at 10:41 AM, Richard Charles wrote: > > Why is the documentation team going down this bizarre path? Do they really > think we will be programming on iPads some day? I hate to beat a dead horse here but there really does seem to be an effort underway to d

Re: Documentation Workflow

> On Nov 17, 2016, at 12:15 PM, Carl Hoefs > wrote: > > Fixing the layout of the documentation doesn't help the core problem, namely, > the way in which it's organized. Each page is so sparse as to be almost > worthless. Well spoken. > You have to drill dow

Re: Documentation Workflow

Dash for iOS has just been open sourced. It's a doc viewer for iPad/iPhone... https://github.com/Kapeli/Dash-iOS On 17 November 2016 at 11:23, Laurent Daudelin wrote: > What’s the 2 “gist” files you are mentioning? > > -Laurent. > -- > Laurent Daudelin > laur...@nemesys-soft.com

Re: Documentation Workflow

What’s the 2 “gist” files you are mentioning? -Laurent. -- Laurent Daudelin laur...@nemesys-soft.com AIM/iChat/Skype:LaurentDaudelin http://www.nemesys-soft.com/

Re: Documentation Workflow

Fixing the layout of the documentation doesn't help the core problem, namely, the way in which it's organized. Each page is so sparse as to be almost worthless. You have to drill down 2, 3, 4 or more links to find the information that you want, dragging the reader through page

Re: Documentation Workflow

Adding this CSS alone increases readability dramatically for the docs pages when viewing from a browser. @namespace url(http://www.w3.org/1999/xhtml); *{font-family:"Tahoma", sans-serif !important;} Whatever Apple's using now looks skinny and is is simply unsettling. Now, if we could only get

Re: Documentation Workflow

On Nov 17, 2016, at 9:13 AM, Slipp Douglas Thompson wrote: > No, you don't need to know HTML or CSS to get this to work. > > Here's a basic step-by-step: > > 1. Download & install the Stylish plugin/add-on/extension for your browser of > choice. The official userstyles.org Stylish is availabl

Re: Documentation Workflow

No, you don't need to know HTML or CSS to get this to work. Here's a basic step-by-step: 1. Download & install the Stylish plugin/add-on/extension for your browser of choice. The official userstyles.org Stylish is available for Chrome ( https://chrome.google.com/webstore/detail/stylish/fjnbnpb

Re: Documentation Workflow

> On Nov 17, 2016, at 6:45 AM, Slipp Douglas Thompson > wrote: [snip] > I got tired of the layout issues and cooked up some quick Stylish CSS to > rectify developer.apple.com/reference/* pages. [snip] > My Stylish CSS (in Mozilla Format) can be found at: > https://gist.github.com/capnslipp

Re: Documentation Workflow

> On Nov 12, 2016, at 10:41 AM, Richard Charles wrote: > > The current documentation seems to be well formatted for display on an iPad. > Does anyone have a programming work flow that uses the documentation > displayed on an iPad or iOS device? Submitted bug report. Probl

Re: Documentation Workflow

On Nov 12, 2016, at 11:41 AM, Richard Charles wrote: > The current documentation seems to be well formatted for display on an iPad. > Does anyone have a programming work flow that uses the documentation > displayed on an iPad or iOS device? > > I suppose if you are commuting t

Re: Documentation Workflow

> On 12 Nov 2016, at 18:41, Richard Charles wrote: > > The current documentation seems to be well formatted for display on an iPad. > Does anyone have a programming work flow that uses the documentation > displayed on an iPad or iOS device? > > I suppose if you are commu

Re: Documentation Workflow

> On Nov 12, 2016, at 11:41, Richard Charles wrote: > > Why is the documentation team going down this bizarre path? Do they really > think we will be programming on iPads some day? I find the overly large format of the Xcode doc viewer to be really hard to parse at a glance. It&

Documentation Workflow

The current documentation seems to be well formatted for display on an iPad. Does anyone have a programming work flow that uses the documentation displayed on an iPad or iOS device? I suppose if you are commuting to work riding a train or a bus and want to review the documentation on your iPad

Re: XCode documentation browser

> On 27 Sep 2016, at 11:01 AM, Graham Cox wrote: > > the browser has started to open everything in Safari Never mind; re-downloading the doc sets has fixed it. —G. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin req

XCode documentation browser

Forgive this non-Cocoa question, but I’m sure the learned folks on this list will be much quicker at pinpointing the issue…. I’m using XCode 7.3.1 on OSX 10.11.6. The built-in documentation browser has always worked fine, and I usually download the doc sets locally so that it’s reasonably fast

CGWindowList Documentation bug?

(NSArray*) CFBridgingRelease(CGWindowListCopyWindowInfo(myWindowListOptions,theWindowID)); myWindowInfoDictionary = [myWindowArray lastObject]; Returns the *ONE* info dictionary for the *ONE* window specified by “theWindowID”. I’ve tested this and it works on 10.10.5 and 10.11 and it works ok. Is this a Bug in th

Re: Help understanding Apple's approach in documentation a little better.

l (to you) private methods exist is an implementation detail subject to change in a future OS release. That may have been the best way to implement class functionality at the time, but since the method isn't in the public header or documentation, Apple is free to remove any or all of those

Re: Help understanding Apple's approach in documentation a little better.

ed methods and properties will ever exist? I think Ken is correct in saying "Their non-presence in the documentation and headers” is what shows them as private. Private is not that same as “not supposed to be there”. ___ Cocoa-dev mailing list (Co

Re: Help understanding Apple's approach in documentation a little better.

On Aug 16, 2015, at 5:35 PM, Ken Thomases wrote: > On Aug 16, 2015, at 4:18 PM, Alex Zavatone wrote: > >> On Aug 16, 2015, at 4:49 PM, Ken Thomases wrote: >> >>> On Aug 16, 2015, at 3:09 PM, Alex Zavatone wrote: >>> >>>> Why i

Re: Help understanding Apple's approach in documentation a little better.

On Aug 16, 2015, at 4:18 PM, Alex Zavatone wrote: > On Aug 16, 2015, at 4:49 PM, Ken Thomases wrote: > >> On Aug 16, 2015, at 3:09 PM, Alex Zavatone wrote: >> >>> Why isn't it in Apple's documentation for storyboards? >> >> Because these are

Re: Help understanding Apple's approach in documentation a little better.

o: >>> designatedEntryPointIdentifier >>> identifierToNibNameMap >>> storyboardFileName >>> name >>> bundle >> >>> This is really great. I can see if any of my view controllers' scenes' >>> identifiers are misspelled,

Re: Help understanding Apple's approach in documentation a little better.

;> bundle > >> This is really great. I can see if any of my view controllers' scenes' >> identifiers are misspelled, I can see what Cocoa's using and verify where or >> if I screwed up somewhere. >> >> This is really useful information. >>

Re: Help understanding Apple's approach in documentation a little better.

ers are misspelled, I can see what Cocoa's using and verify where or > if I screwed up somewhere. > > This is really useful information. > > Why isn't it in Apple's documentation for storyboards? Because these are private implementation details. They are subject to

Help understanding Apple's approach in documentation a little better.

ForgotPassword.storyboardc; name: NSString = ForgotPassword; bundle: NSBundle = NSBundle (loaded); }] This is really great. I can see if any of my view controllers' scenes' identifiers are misspelled, I can see what Cocoa's using and verify where or if I screwed up somewhere. Th

Re: Latest Documentation for adding Applescript Support to an Objective-C Project

On 24 Feb 2015, at 8:40 pm, Dave wrote: > > I’m wondering why I got a warning when I downloaded the sample Apps then? Sounds odd. I just downloaded a couple again, with no problems other than build settings that needed to be updated. -- Shane Stanley __

Re: Latest Documentation for adding Applescript Support to an Objective-C Project

> On 23 Feb 2015, at 23:29, Shane Stanley wrote: > > On 24 Feb 2015, at 12:21 am, Dave wrote: >> >> From searching online it looks like things have changed quite recently? > > Not in terms of how it's implemented in apps. I’m wondering why I got a warning when I downloaded the sample Apps th

Re: Latest Documentation for adding Applescript Support to an Objective-C Project

On 24 Feb 2015, at 12:21 am, Dave wrote: > > From searching online it looks like things have changed quite recently? Not in terms of how it's implemented in apps. -- Shane Stanley ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do no

Latest Documentation for adding Applescript Support to an Objective-C Project

Hi, I’m a bit confused as to where the latest documentation and sample code for adding Applescript support to an Objective-C Project. From searching online it looks like things have changed quite recently? When I downloaded the Sample AS App’s from the Apple Developer Site, I got a warning

Re: Cocoa Documentation PlugIn for Safari

Found it! http://www.erinedesign.com/extensions/ If anyone is looking for the same thing. All the Best Dave > On 17 Feb 2015, at 11:13, Dave wrote: > > Hi All, > > A while back I Installed a plug in for Safari that showed the Cocoa Reference > Documents and allow searching etc. When I upd

Cocoa Documentation PlugIn for Safari

Hi All, A while back I Installed a plug in for Safari that showed the Cocoa Reference Documents and allow searching etc. When I updated to Yosemite/XCode 6 it seems to have gone missing (not sure why?). I tried to find it again but not having much luck, does anyone know where these PlugIns live

Re: View hierarchy, documentation, and origin location.

On Sep 24, 2013, at 8:33 PM, Peter Teeson wrote: > On 2013-09-24, at 9:05 PM, Peter Teeson wrote: >> It would be nice if the documentation for NSMatrix mentioned that in the >> Overview. >> For example "NSMatrix uses flipped coordinates" would have saved everyone

Re: View hierarchy, documentation, and origin location.

On 2013-09-24, at 9:05 PM, Peter Teeson wrote: > It would be nice if the documentation for NSMatrix mentioned that in the > Overview. > For example "NSMatrix uses flipped coordinates" would have saved everyone > from my noise. 15073135 Documentation Enhancement reques

Re: View hierarchy, documentation, and origin location.

the coordinates probably because of the zero origin indexing of the cells. Of course with the help from the comments here and 20/20 hindsight I should have done this first. It would be nice if the documentation for NSMatrix mentioned that in the Overview. For example "NSMatrix uses fl

Re: View hierarchy, documentation, and origin location.

On 2013-09-24, at 1:26 PM, Gary L. Wade wrote: > The object you created has an inset of 40, and since NSMatrix organizes its > cells from the top left, > that is what you are seeing, regardless of whether or not NSMatrix returns > YES for -isFlipped. > If this is a matter of personal discovery, o

Re: View hierarchy, documentation, and origin location.

On 24 Sep 2013, at 18:26, Gary L. Wade wrote: > The object you created has an inset of 40, and since NSMatrix organizes its > cells from the top left, that is what you are seeing, regardless of whether > or not NSMatrix returns YES for -isFlipped. If this is a matter of personal > discovery, o

Re: View hierarchy, documentation, and origin location.

as follows: > Document windowControllerDidLoadNib > Frame 0 ,0, 500, 500; Bounds 0, 0, 500, 500 > > Matrix drawRect:(NSRect)dirtyRect > Frame 40, 40, 420, 420; Bounds 0, 0, 40, 40 > > (6) So I must be missing something in my understanding of the documentation. > My thinkin

Re: View hierarchy, documentation, and origin location.

of the frame and bounds rects are as follows: Document windowControllerDidLoadNib Frame 0 ,0, 500, 500; Bounds 0, 0, 500, 500 Matrix drawRect:(NSRect)dirtyRect Frame 40, 40, 420, 420; Bounds 0, 0, 40, 40 (6) So I must be missing something in my understanding of the documentation. My thinkin

Re: View hierarchy, documentation, and origin location.

On Mon, Sep 23, 2013, at 06:20 PM, Peter Teeson wrote: > > On 2013-09-23, at 1:36 PM, Kyle Sluder wrote: > > What’s _theMatrix’s frame? > Here once again is the code I posted That's not what I asked. I asked for the frame. > It's values happen to be 40.0 40.0 500.0 500.0 Thank you for answering

Re: View hierarchy, documentation, and origin location.

7 > > If you look at the code I posted along with my comments you will see that > I get the windows content view frame, inset it and use that as the matrix > frame. > (The matrix is also a View per NSMatrix docn) > > It's values happen to be 0, 0, 500, 500 and, based on

Re: View hierarchy, documentation, and origin location.

On 2013-09-23, at 1:36 PM, Kyle Sluder wrote: > What’s _theMatrix’s frame? Here once again is the code I posted NSWindow *theWindow = [aController window]; NSView *theContentView = theWindow.contentView; NSRect theContentFrame = theContentView.frame; NSRect theMatrixFrame =

Re: View hierarchy, documentation, and origin location.

r NSMatrix docn) It's values happen to be 0, 0, 500, 500 and, based on the documentation I quoted, I anticipated that it would draw from the lower left of the content view. It doesn't! It draws from the top left of the content view (which is a View per NSWindow docn) Why is that? What am

Re: View hierarchy, documentation, and origin location.

> On Sep 23, 2013, at 9:09 AM, Peter Teeson wrote: > > My questions: > (0) Given the above documentation why is the matrix drawn at top left > (indented of course)? What’s _theMatrix’s frame? It could either have an origin that puts it at the top, or it could draw its conte

Re: View hierarchy, documentation, and origin location.

Probably more to do with the NeXTSTEP/OPENSTEP ancestry. Those used Display Postscript with the origin being the bottom left. Gerd On Sep 23, 2013, at 1:19 PM, Dave wrote: > > On 23 Sep 2013, at 17:09, Peter Teeson wrote: >> >> Peter >> >> PS: If my memory is correct, from the beginning of

Re: View hierarchy, documentation, and origin location.

On 23 Sep 2013, at 19:50, Gerd Knops wrote: > Probably more to do with the NeXTSTEP/OPENSTEP ancestry. Those used Display > Postscript with the origin being the bottom left. > > Gerd Yes, you're right it was because of PostScript, although you'd chose to an upside down screen coordinate syst

Re: View hierarchy, documentation, and origin location.

On 23 Sep 2013, at 17:09, Peter Teeson wrote: > > Peter > > PS: If my memory is correct, from the beginning of Mac OS up till OS X the > origin was top left. Yes, Quartz changed it to be bottom left for some crazy reason - maybe just to be different and upset off the Carbon developers of the

Re: View hierarchy, documentation, and origin location.

e.com/ On Sep 23, 2013, at 9:09 AM, Peter Teeson wrote: > (0) Given the above documentation why is the matrix drawn at top left > (indented of course)? > The default location is stated to be lower left. ___ Cocoa-dev mailing list (Cocoa-dev@l

View hierarchy, documentation, and origin location.

atrix alloc]initWithFrame:theMatrixFrame mode:NSListModeMatrix prototype:protoCell numberOfRows:3 numberOfColumns:3]; [theContentView addSubview:_theMatrix]; } My questions: (0) Given the above documentation why is the matrix drawn at top left (indented of course)? The default loca

Re: "Provide Feedback" on documentation pages is broken

ole Provide Feedback mechanism is still > broken, or perhaps not yet re-enabled, after the recent dev portal shutdown. > > If it isn't fixed soon I'll just submit a documentation Radar. > > --Andy > > On Aug 14, 2013, at 10:27 PM, Alex Zavatone wrote: > >>

Re: "Provide Feedback" on documentation pages is broken

I was in the Mac OS section. I tested on another page (NSObject) and that failed too. I wonder if the whole Provide Feedback mechanism is still broken, or perhaps not yet re-enabled, after the recent dev portal shutdown. If it isn't fixed soon I'll just submit a documentation Rada

Re: "Provide Feedback" on documentation pages is broken

Same thing happened to me yesterday trying to add a note to update the iOS Reachability example to ARC. Were you in the iOS section, the Mac OS section or another section of the doc pages? Do you think that all the Provide Feedback links might be broken like this? On Aug 14, 2013, at 10:20 AM

"Provide Feedback" on documentation pages is broken

I tried using the "Provide Feedback" link on one of the dev doc pages and got this: I filed a Radar about it: #14735067, in case anyone wants to dupe it, assuming it's not just me. --Andy ___ Cocoa-dev mailing list (Coc

CoreGraphics Image I/O Documentation

Hi, Just checked on lists for an e-mail list on CoreGraphics or Image I/O without seeing an obviously appropriate list. So since I'm already subscribed here I thought I'd give this list a shot. In the header file for CGImageSource.h the only key that is listed as appropriate for the options di

Re: The Documentation says "that is a member variable" SOLVED

OH good grief - I've been at my terminal too long - The declaration syntax is just wrong WRONG: @property (UITextField *) activeField; CORRECT: @property UITextField * activeField; Sorry for the bother YT On Jul 4, 2013, at 5:41 PM, YT wrote: > In the online document "Managing the K

The Documentation says "that is a member variable"

In the online document "Managing the Keyboard" under the heading "Moving Content That is Located Under the Keyboard" There is some nifty code listings Listing 4-1 Handling the keyboard notifications Listing 4-2 Additional methods for tracking the active text field. AND there is some explana

Re: What am I looking for in the documentation?

It should go without saying that the "text" char array you suggest must already exist, and be at least one char longer than the longest string you expect (I'd make it twice as long). And use snprintf(3) instead. Bad People (or you) will try to overrun the buffer if you don't prevent it. (Not li

Re: What am I looking for in the documentation?

You might want to look at sprintf . sprintf(text, "%f", fv) should work just fine. On Sat, May 4, 2013 at 4:20 PM, YT wrote: > I have need to turn a local float value into a char array. > > That is, The Quartz 2D graphics function requires the passing of a (c

Re: What am I looking for in the documentation?

On May 4, 2013, at 4:20 PM, YT wrote: > I have need to turn a local float value into a char array. > > That is, The Quartz 2D graphics function requires the passing of a (const > char *) to a text string or I was thinking of a character array. Knowing which API you mean, I would recommend ag

Re: What am I looking for in the documentation?

On May 6, 2013, at 09:03 , Sean McBride wrote: > Also consider localisation... do you absolutely want the '.' character, or > whatever decimal character is specified by the user's locale (or the user > himself)? Consider NSNumberFormatter if you want localisation. Yes! I don't know what I wa

Re: What am I looking for in the documentation?

On Sat, 4 May 2013 16:20:14 -0700, YT said: >I have need to turn a local float value into a char array. > >That is, The Quartz 2D graphics function requires the passing of a >(const char *) to a text string or I was thinking of a character array. > >My mind is mush at the moment - can't seem to r

Re: What am I looking for in the documentation?

Thanks! sprintf worked great - Didn't realize that those wonderful Standard C functions were available. Again, Thanks YT On May 4, 2013, at 4:23 PM, Mohit Sharma wrote: > You might want to look at sprintf. sprintf(text, "%f", fv) should work just > fine. > > > On Sat, May 4, 2013 at

Re: What am I looking for in the documentation?

You need to do a string conversion, just like you would in any situation where you need a textual version of a number. One possible way: NSString* s = [NSString stringWithFormat: @"%.1f", fv]; const char* sp = s.UTF8String; another: char* s[16]; snprintf(s, 16,

What am I looking for in the documentation?

I have need to turn a local float value into a char array. That is, The Quartz 2D graphics function requires the passing of a (const char *) to a text string or I was thinking of a character array. My mind is mush at the moment - can't seem to recall the way to program a conversion of float

[ANN] Automation documentation archive and wiki

Hi The OS X application automation archive is an up-dateable archive of OS X automation documentation: http://www.mugginsoft.com/automation The archive provides online browsable AppleScript and ScriptingBridge documentation for a range of OS X applications, e.g. Photoshop: http

[ANN] Online ScriptingBridge documentation archive

The ScriptingBridge is a great way to automate applications either from Obj-C or from a Cocoa language (either a bridge or a native implementation such as F-script or Nu). We are establishing an online archive of browsable ScriptingBridge and AppleScript derived documentation to assist with

Re: predicates and sort descriptors for NSFetchRequest - documentation is a bit vague

Let's call the relation "tob" so my sort descriptor said >> withKey:@"tob.b" and it results of the fetch request did not come back in >> that order, but if I then sort the resulting array using the sort >> descriptor, it does sort it. >> &

Re: predicates and sort descriptors for NSFetchRequest - documentation is a bit vague

Key:@"tob.b" and it results of the fetch request did not come back in > that order, but if I then sort the resulting array using the sort descriptor, > it does sort it. > > The way I read the documentation, that should work during the fetch, but it > doesn't. Unf

Re: predicates and sort descriptors for NSFetchRequest - documentation is a bit vague

fetch request." >> bothers me as I see lots of examples where they are used in books on Core >> Data. > > The key phrase here is "Objective-C-based." I believe the documentation is > making a distinction between the full functionality of NSPredicate and > NSSo

Re: predicates and sort descriptors for NSFetchRequest - documentation is a bit vague

ch directly, you should typically not add > Objective-C-based predicates or sort descriptors to the fetch request." > bothers me as I see lots of examples where they are used in books on Core > Data. The key phrase here is "Objective-C-based." I believe the documentation is makin

predicates and sort descriptors for NSFetchRequest - documentation is a bit vague

s; however, if I apply the sort descriptor to the resulting array, it does work. I then read this link: http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/CoreData/Articles/cdFetching.html which states: You cannot fetch using a predicate based on transient properties (althoug

Re: Does XCode 3.2 Documentation Browser Stink?

ld use to the left of the actual > documentation, you now use the breadcrumb links towards the top of the > documentation. It took me a while to get accustomed to it, but in the end you > have more room for your documentation text. > >> Am I missing something or does the new Doc

Re: Does XCode 3.2 Documentation Browser Stink?

Instead of the the links you would use to the left of the actual documentation, you now use the breadcrumb links towards the top of the documentation. It took me a while to get accustomed to it, but in the end you have more room for your documentation text. > Am I missing something or does

Re: NSNumberFormatter documentation error?

Thanks for the clarification. Andre Masse > It's not a matter of misinterpretation per se. The documentation reflects the > API, and would apply only to objects you create in your own code. Interface > Builder may choose to have its own defaults for objects created by it, and &

Re: NSNumberFormatter documentation error?

On Jul 30, 2011, at 9:09 AM, Andre Masse wrote: > According to the NSNumberFormatter documentation: > > setGeneratesDecimalNumbers: > Controls whether the receiver creates instances of NSDecimalNumber when it > converts strings to number objects. > > - (void)setGenerate

NSNumberFormatter documentation error?

Hi, According to the NSNumberFormatter documentation: setGeneratesDecimalNumbers: Controls whether the receiver creates instances of NSDecimalNumber when it converts strings to number objects. - (void)setGeneratesDecimalNumbers:(BOOL)flag Parameters flag YES if the receiver should generate

Re: Help finding documentation about printing

On 11-Jul-2011, at 11:05 PM, Christopher Henrich wrote: > > On Jul 10, 2011, at 12:48 PM, Joel Norvell wrote: > >> Hi Christopher, >> >> The documentation set on >> >> http://developer.apple.com/devcenter/mac/index.action >> >> has

Re: Help finding documentation about printing

On Jul 10, 2011, at 12:48 PM, Joel Norvell wrote: > Hi Christopher, > > The documentation set on > > http://developer.apple.com/devcenter/mac/index.action > > has Apple's printing giude. > > The full URL to the printing section is: > > http://develope

Re: Help finding documentation about printing

Hi Christopher, The documentation set on http://developer.apple.com/devcenter/mac/index.action has Apple's printing giude. The full URL to the printing section is: http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/Printing/Printing.html%23//apple_ref/doc/uid/1000

Help finding documentation about printing

t read Mac OS X Printing System Overview I am glad to comply; but where is that Overview? I have searched for it in the documentation that accompanies Xcode, without success. All that I can find is a few other instructions that the reader of another document should begin by reading this Overview. U

Re: Documentation generation

ave > > Sent from my iPhone > > On May 8, 2011, at 4:42 AM, Thomas Davie wrote: > >> Heya, >> >> I'm working on improving my CoreParse >> (http://www.github.com/beelsebob/CoreParse) framework by actually >> documenting it properly. The pr

Re: Documentation generation

documenting > it properly. The problem I'm hitting though is that either the two major > documentation generators suck (doubt that, probably PEBKAC), or their default > configuration sucks. I've had a go with both doxygen and headerdoc. > > Headerdoc seems to produc

Documentation generation

Heya, I'm working on improving my CoreParse (http://www.github.com/beelsebob/CoreParse) framework by actually documenting it properly. The problem I'm hitting though is that either the two major documentation generators suck (doubt that, probably PEBKAC), or their default configura

Re: Error in documentation: Cocoa Drawning Guide

At the bottom of the docs page is a "did this help" set of links. That leads you to a place you can file documentation comments On May 4, 2011, at 13:51, Дмитрий Николаев wrote: > Hello! > > I dont know where to post such errors. > In > http://developer.apple.com/l

Error in documentation: Cocoa Drawning Guide

Hello! I dont know where to post such errors. In http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/CocoaDrawingGuide/Paths/Paths.html Paths. Line Dash Style Listing 5-5 Adding a dash style to a path // Set the line dash pattern. float lineDash[6]; float need to

Re: Documentation Hard Copy?

Followup: I got my hard copy from lulu.com today -- 628 pages of HIG/tutorial docs, perfect bound on A4 for USD22 + USD10 shipping to Australia (they may have printed it here, not sure). It's a chunky volume (reminds my of Inside Mac :-) but the per-volume costs discouraged me from printing the

  1   2   3   >