• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: sandboxing and filename extensions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: sandboxing and filename extensions


  • Subject: Re: sandboxing and filename extensions
  • From: Scott Ribe <email@hidden>
  • Date: Wed, 15 May 2013 09:31:39 -0600

On May 15, 2013, at 1:03 AM, Quincey Morris wrote:

> Could you clarify a couple of things…
>
> Are you typing the file name into the Save panel, or just pressing Enter to use the pre-filled name? What are the settings for "canSelectHiddenExtension" and "isExtensionHidden"? What is the behavior on 10.8.3?

Typing the file name in. In fact, although I hadn't tried it until you made me think of it, pre-filling the name (with setNameFieldStringValue:) does not work in a sandboxed app. I do not set the options about hidden extensions--I do not want this dialog to be different than the system default. The behavior on 10.8.3 is the same in all cases.

Also, I earlier tried fiddling with the options about hidden extensions, and that made no difference. And I changed my Finder preferences back to default, turning off "show all file extensions", and that made no difference.

> I seem to recall noticing a change in behavior in some system version, where the save panel no longer added the extension when it was missing. This was either on the initial file name pre-filled in the panel, or on entering an extension-less name when the checkbox indicating "isExtensionHidden" was unchecked, or something like that. But my recollection on this is very hazy, sorry.
>
> Does it make any difference if you use the UTI for PDF files instead of the literal string "PDF" for the extension? We already know that the powerbox Save panel doesn't implement everything the regular one does, and it may have some limitations for non-UTI type strings.

Using @"com.adobe.pdf" makes no difference.

I guess about the only thing I can do here in order to get the file named in a usable manner (since Apple so wisely ditched _all_ support for "old-fashioned" file types), is to use a delegate, implement panel:validateURL:error:, and force the user to type ".pdf". Ugh.

--
Scott Ribe
email@hidden
http://www.elevated-dev.com/
(303) 722-0567 voice





_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden


  • Follow-Ups:
    • Re: sandboxing and filename extensions
      • From: Charles Srstka <email@hidden>
    • Re: sandboxing and filename extensions
      • From: Quincey Morris <email@hidden>
References: 
 >sandboxing and filename extensions (From: Scott Ribe <email@hidden>)
 >Re: sandboxing and filename extensions (From: Quincey Morris <email@hidden>)

  • Prev by Date: Getting a splash screen to show
  • Next by Date: Re: Getting a splash screen to show
  • Previous by thread: Re: sandboxing and filename extensions
  • Next by thread: Re: sandboxing and filename extensions
  • Index(es):
    • Date
    • Thread