> On 2 Jun 2015, at 7:39 am, Quincey Morris > <quinceymor...@rivergatesoftware.com> wrote: > > What’s a non-URL path? AFAIK a URL** always contains a path, even if only > relative, and even if surrounded by other stuff.
> If you look at the header file for NSPathControlItem, it has a URL property > that appears to URL-ify the path in spite of your data. > >> I still need to tweak the icons to match it. > > There are actually 3 cases, I think: > > 1. The control’s URL is not a file URL. > > 2. The control’s URL is a file URL for a file that exists. > > 3. The control’s URL is a file URL for a file that doesn’t exist. > 4. The control represents a “path” that isn’t anything like a URL, such as a tree node (e.g. a NSIndexPath or something equivalent). Like Lee Ann, I use a NSPathControl for this. Forcing the data it represents to be a URL is making it a lot more limited than its original design. —Graham _______________________________________________ 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
