Re: Help Indexing
> On 2017 Apr 13, at 16:46, Frank D. Engel, Jr.wrote: > > Hi, I am trying to create an Apple Help book … help buttons on the interface > trying to access specific pages using anchors, and these are not working. > > I generated an index using the "hiutil" command, and when I reran that and > enabled verbose output (hiutil -Cavv ...), I got a bunch of output like this: > > > Contents/Resources/English.lproj/pgs/doc70.html -- Parse error: The operation > couldn’t be completed. (NSXMLParserErrorDomain error 76.) > ... > > The pages open just fine in a web browser, but it looks like the hiutil > command is trying to parse it as XML? That obviously won't work... these are > regular HTML files, not XML. I’ve been down this road. As you’ve surmised, your anchors are probably failing because your help book is not being indexed. The reason why it is not being indexed is because hiutil is much more strict than a web browser. You need to get rid of those Parse errors, every single one of them. Don’t worry about XML. If I recall correctly, when I ran my pages through a good HTML syntax checker like https://validator.w3.org, it showed me the issues and after I fixed them and the syntax checker was happy, hiutil was happy, and all my anchor buttons worked. There may have ben other details I forgot, so if someone else wants to jump in, please do. ___ 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
Help Indexing
Hi, I am trying to create an Apple Help book. It is working if I choose the help option from my application's Help menu, but I have some help buttons on the interface trying to access specific pages using anchors, and these are not working. I generated an index using the "hiutil" command, and when I reran that and enabled verbose output (hiutil -Cavv ...), I got a bunch of output like this: Contents/Resources/English.lproj/pgs/doc70.html -- Parse error: The operation couldn’t be completed. (NSXMLParserErrorDomain error 76.) Contents/Resources/English.lproj/pgs/doc70.html -- Parse error: Error 76, Description: The operation couldn’t be completed. (NSXMLParserErrorDomain error 76.), Line: 124, Column: 9 Contents/Resources/English.lproj/pgs/doc70.html -- Parse error: The operation couldn’t be completed. (NSXMLParserErrorDomain error 76.) Contents/Resources/English.lproj/pgs/doc70.html -- Parse error: Error 76, Description: The operation couldn’t be completed. (NSXMLParserErrorDomain error 76.), Line: 125, Column: 8 Contents/Resources/English.lproj/pgs/doc70.html -- Parse error: The operation couldn’t be completed. (NSXMLParserErrorDomain error 5.) Contents/Resources/English.lproj/pgs/doc70.html -- Parse error: Error 5, Description: The operation couldn’t be completed. (NSXMLParserErrorDomain error 76.), Line: 125, Column: 8 The pages open just fine in a web browser, but it looks like the hiutil command is trying to parse it as XML? That obviously won't work... these are regular HTML files, not XML. This is what I am using in the application to access the individual topics (this is in a method receiving "what" as a parameter): NSString *locBookName = [[NSBundle mainBundle] objectForInfoDictionaryKey: @"CFBundleHelpBookName"]; [[NSHelpManager sharedHelpManager] openHelpAnchor:what inBook:locBookName]; What am I missing here? ___ 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
Re: NSProgressIndicator indeterminate
> On Apr 13, 2017, at 13:35 , Tom Doanwrote: > > > > the indeterminate one has an almost imperceptibly lighter > > medium-dark moving over medium-dark. > > This suggests you have set your system appearance to Graphite instead > of Blue (in System Preferences -> General), and it may well be that in > the graphite version it´s harder to see the animation than in the > default blue. Your physical environment (lighting conditions, monitor > age, etc) might also have some effect on what you see. However, it´s > hard to say whether your users will or will not see the animation. > > IMO, it´s not worth worrying about the problem. Apple has decided > that this new style of indeterminate progress is suitable, so it´s > not your fault if they´re wrong. Anything clever you do to change > the appearance could easily break the next time Apple tweaks control > appearances. > > If you feel that it´s going to be a problem for users, then you > could use the spinning version of the indeterminate progress control, > instead of or in addition to the bar version. Thanks. I do indeed have Graphite rather than Blue, though Blue is same basic problem in Blue. However, the spinning wheel works fine, so I switched to that. --- 1560 Sherman Ave #1029 Evanston, IL 60201 USA ___ 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
NSProgressIndicator indeterminate
I've been using determinate NSProgressIndicators for years and those seem to work fine. I recently added a indeterminate one for a particular operation. On first (and second and third) takes, I thought it wasn't working. Then I looked *really* closely and found that there actually is a *very* slight gradient moving across the bar. While the determinate bar is medium-dark gray moving over light gray, the indeterminate one has an almost imperceptibly lighter medium-dark moving over medium-dark. This seems less than ideal. Is there some setting that can change that? Tom Doan --- 1560 Sherman Ave #1029 Evanston, IL 60201 USA ___ 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
Re: Xcode Cocoa Windows
On Apr 13, 2017, at 03:04 , LAURENT Charleswrote: > > How to proceed next to get a single window ? Delete the storyboard, then create a new file for your project. In the file-type dialog, choose Application from the UI section, and you’ll get a XIB file like the one that the templates used to provide. ___ 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
Xcode Cocoa Windows
Hello, My question concerns Xcode Interface : the choice between 1 window and storyBoard The book Apress copyright 2017 macOS Programming for Absolute Beginners Wallace Wang still creates projects using the choice between 1 window and storyBoard The recent update of Xcode Version 8 3 1 apparently creates at first only projects with storyBoard How to proceed next to get a single window ? Thank you very much Charles ___ 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