On May 30, 2012, at 10:54 PM, Marco S Hyman wrote:
3. When I use -setDirectoryURL: and the URL is somewhere in my sandbox, the
actual URL displayed is the old location, back in ~/Library/Application
Support (!)
When using a sandbox in Mac OS X 10.7 and later, the home directory is the
On May 31, 2012, at 2:43 PM, Alex Zavatone wrote:
So, before I start waving my hands in the air, running around the office and
panicking, does this mean that the user can not save files where ever he/she
wants to on the HD in future versions of the Mac OS?
No, it's completely and totally
On May 31, 2012, at 5:46 PM, Kyle Sluder wrote:
On May 31, 2012, at 2:43 PM, Alex Zavatone wrote:
So, before I start waving my hands in the air, running around the office and
panicking, does this mean that the user can not save files where ever he/she
wants to on the HD in future
On May 31, 2012, at 2:46 PM, Kyle Sluder wrote:
On May 31, 2012, at 2:43 PM, Alex Zavatone wrote:
So, before I start waving my hands in the air, running around the office and
panicking, does this mean that the user can not save files where ever he/she
wants to on the HD in future
On May 31, 2012, at 5:46 PM, Kyle Sluder wrote:
On May 31, 2012, at 2:43 PM, Alex Zavatone wrote:
So, before I start waving my hands in the air, running around the office and
panicking, does this mean that the user can not save files where ever he/she
wants to on the HD in future
In my app I put up a save panel to save a file in a particular place within my
~/Library/Application Support folder. When not sandboxed, this works fine. When
sandboxed, the URL that is set in the panel is correct (it's inside the sandbox
now), but the save panel doesn't appear. In fact, it
[savePanel beginSheetModalForWindow:[self windowForSheet]
completionHandler:completionHandler];
Anyone else come across this issue? My understanding is that with sandboxing,
the save panel is a bit more involved since it has to open up holes in the
sandbox on behalf of the user,
On 31/05/2012, at 9:57 AM, Graham Cox wrote:
So, internally the panel is throwing an exception, due to a nil object. But
why? what am I doing wrong here?
OK, some more discoveries.
1. The problem only occurs with a delegate set on the panel. The delegate isn't
called - just its presence
On May 30, 2012, at 7:54 PM, Marco S Hyman m...@snafu.org wrote:
In a sandboxed app that will be
/Users/user/Library/Containers/app/Data/Documents/
What? No! The whole point of sandboxing and NSSavePanel is that Powerbox will
poke holes into the user's *actual* Documents directory.
Graham,
On 31/05/2012, at 12:54 PM, Marco S Hyman wrote:
The user doesn't know or care what the actual path is. Why are you
trying to show it in a save dialog.
I don't, as such, but the save panel shows the full path and it's simply wrong.
I have a specific location inside my Application Support
P.S. Just saw this:
http://www.macworld.com.au/news/ac-devs-air-frustrations-at-mac-app-store-sandboxing-debacle-55502/
I would say that's a pretty reasonable article about the current state of
sandboxing as I understand it. I've given up for a while on the OSX thing I was
writing
11 matches
Mail list logo
