Graham,
Thanks for your fast response.
I'll look at this ASAP, and will let you know how it goes :-)
Cheers,
Gilles
On Jun 12, 2012, at 2:27 AM, Graham Cox wrote:
On 12/06/2012, at 12:29 AM, Gilles Celli wrote:
the sheet is properly displayed (with its TextField and button) for the
Hi list
Our app allows to export its documents in a variety of formats, such as jpeg,
tiff, png, pdf . Hence, we have set up the NSSavePanel to sport a file types
popup that allows the user to select the desired file type.
Now we want that save panel to remember the format of the last export
Yes, I was using beginSheetModalForWindow: completionHandler
So I have changed to:
[NSApp beginSheet:op modalForWindow:[self window] modalDelegate:self
didEndSelector:@selector(sheetDidEnd:returnCode:contextInfo:) contextInfo:nil];
- (void)sheetDidEnd:(NSWindow *)sheet
On 12 Jun 2012, at 11:00, koko wrote:
Yes, I was using beginSheetModalForWindow: completionHandler
So I have changed to:
[NSApp beginSheet:op modalForWindow:[self window] modalDelegate:self
didEndSelector:@selector(sheetDidEnd:returnCode:contextInfo:)
contextInfo:nil];
-
op is an NSOpenPanel
[self window] is an NSWindow owned by a NSWindowController subclass
-koko
On Jun 12, 2012, at 12:20 PM, Mike Abdullah wrote:
On 12 Jun 2012, at 11:00, koko wrote:
Yes, I was using beginSheetModalForWindow: completionHandler
So I have changed to:
[NSApp
I have international users who may have things like umlaut in file names /
paths which I may get as CStrings given our Model.
What NS string encoding should be used to preserve the umlaut and not crash? Is
NSUTF8 OK?
-koko
___
Cocoa-dev mailing
On 12 Jun 2012, at 12:42 PM, koko wrote:
I have international users who may have things like umlaut in file names /
paths which I may get as CStrings given our Model.
What NS string encoding should be used to preserve the umlaut and not crash?
Is NSUTF8 OK?
UTF-8 can represent any
Hi,
I just moved to Lion and its new XCode 4. I'm calling the compiler
directly, so no XCode processing. I basically cloned the way XCode uses the
compiler. For x86 everything works just fine, in fact CLANG seems to have
the same options as GCC used before. But with x64 it ends up with weird
When dealing with the file system pathnames, you should use the file system
representation methods from NSString/NSFileManager.
Specifically, -[NSFileManager fileSystemRepresentationWithPath:] and
-[NSFileManager stringWithFileSystemRepresentation:].
Aki
On 2012/06/12, at 12:42, koko
OK. NSUTF8 it is. I just sent a beta to Norway so I'll know more in the next
24 hours.
-koko
On Jun 12, 2012, at 3:13 PM, Stephane Sudre wrote:
Do you have examples in mind where the result of - [NSFileManager
fileSystemRepresentationWithPath] differs from the one of - [NSString
All the accented chars, for example, are represented differently.
Aki Inoue
On 2012/06/12, at 14:43, koko k...@highrolls.net wrote:
OK. NSUTF8 it is. I just sent a beta to Norway so I'll know more in the
next 24 hours.
-koko
On Jun 12, 2012, at 3:13 PM, Stephane Sudre wrote:
On 13/06/2012, at 4:34 AM, koko wrote:
op is an NSOpenPanel
that class has its own -beginSheetModal... method - you should use that.
--Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator
I could, if there were an official api to get that NSPopUpButton. Is there? I
did not find one.
Kurt
On 12. Jun 2012, at 23:15, Martin Wierschin wrote:
Our app allows to export its documents in a variety of formats, such as
jpeg, tiff, png, pdf . Hence, we have set up the NSSavePanel to
Are you using a pre-built export dialog or a standard save dialog with a custom
accessory view? Sounds like you need to use a custom accessory view, although
this would most likely require you to code all the export features.
Todd
On Jun 12, 2012, at 10:11 PM, Kurt Sutter wrote:
I could, if
14 matches
Mail list logo
