> On 2015 Jan 16, at 21:34, Ken Thomases wrote:
>
> How about, instead of calling through to super, you simply implement those
> methods in the straightforward way by running the Open panel. For
> -runModalOpenPanel:forTypes:, set the directoryURL as you want, set
> allowedFileTypes with the
On Jan 16, 2015, at 3:53 AM, Jerry Krinock wrote:
> Also, I’d forgotten about -[NSSavePanel setDirectoryURL:]. TextEdit does not
> invoke this method, so that does not explain the behavior. And yes I agree
> that overriding both -runModalOpenPanel:forTypes: and
> -beginOpenPanel:forTypes:com
Just to clarify … this thread is about code, not about design. The appropriate
initial directory
offered by File > Open under various conditions is a design decision. The
answer may vary for different apps.
This thread is about the code that you write, or don’t, after the design
decision is m
On 16 Jan 2015, at 01:16, Jerry Krinock wrote:
>> So, great, I thought, just override -currentDirectory in the
>> NSDocumentController subclass for TextEdit, and I can make it go wherever I
>> want to.
> Have you thought about just setting the directoryURL of the NSOpenPanel?
If you do that,
On 16 Jan 2015, at 01:16, Jerry Krinock wrote:
> So, great, I thought, just override -currentDirectory in the
> NSDocumentController subclass for TextEdit, and I can make it go wherever I
> want to.
Have you thought about just setting the directoryURL of the NSOpenPanel?
> But, no. Although
Yes, I missed that NSNavLastRootDirectory default. That explains the magic.
Also, I’d forgotten about -[NSSavePanel setDirectoryURL:]. TextEdit does not
invoke this method, so that does not explain the behavior. And yes I agree
that overriding both -runModalOpenPanel:forTypes: and
-beginOpen
> On 2015/01/16, at 11:24, Quincey Morris
> wrote:
>
> Only if it actively interferes with the way your users actually use your app
> (and they’re complaining about it) could I see an unarguable reason for going
> your own way on this.
I can see a lot of reasons a particular NSDocument subc
On Jan 15, 2015, at 16:16 , Jerry Krinock wrote:
>
> Presumably I could get the control I want by overriding and re-implementing
> -openDocument: to actually use -currentDirectory the way the documentation
> says it should.
I’m not entirely sure you should do that, at least not casually.
Not
On Jan 15, 2015, at 4:34 PM, Ken Thomases wrote:
> On Jan 15, 2015, at 6:16 PM, Jerry Krinock wrote:
>
>> I have noticed that the directory which is navigated to in the File > Open
>> dialog of my NSDocument-based application does not give what I expect, and
>> am trying to control it.
>
>>
On Jan 15, 2015, at 6:16 PM, Jerry Krinock wrote:
> I have noticed that the directory which is navigated to in the File > Open
> dialog of my NSDocument-based application does not give what I expect, and am
> trying to control it.
> So, great, I thought, just override -currentDirectory in the
I have noticed that the directory which is navigated to in the File > Open
dialog of my NSDocument-based application does not give what I expect, and am
trying to control it. To make sure it’s not due to something I did, I am
experimenting with Apple’s TextEdit sample project instead.
Although
11 matches
Mail list logo
