> On 27 Mar 2015, at 14:34, Alex Kac wrote:
>
> I'm trying to get rid of NSOutlineView horizontal separator lines.
> I've tried the following with no luck.
>
> self.outlineView.gridStyleMask = NSTableViewGridNone;
> self.outlineView.gridColor = [NSColor clearColor];
> self.outlineView.intercell
I'm trying to get rid of NSOutlineView horizontal separator lines.
I've tried the following with no luck.
self.outlineView.gridStyleMask = NSTableViewGridNone;
self.outlineView.gridColor = [NSColor clearColor];
self.outlineView.intercellSpacing = NSZeroSize;
https://www.dropbox.com/s/f6eteh5wgrou
Yes, my specific task is to make this run on all versions of OS X
starting with 10.6, including 10.10.
I have the sense - I don't specifically know - that my client is new
to OS X development. Maybe he used a storyboard because that's what
he thought he was supposed to do.
I can fix his problem
I think the problem is storyboards are not available prior to 10.10
Is that going to run on anything earlier?
Sent from my iPhone
> On 2015/03/27, at 13:26, Michael Crawford wrote:
>
> Xcode wanted the storyboard to be within a folder called "en.lproj".
> Previously it was in a folder called "B
Xcode wanted the storyboard to be within a folder called "en.lproj".
Previously it was in a folder called "Base".
I removed the reference to the storyboard from my project, then in the
Finder I renamed the "Base" folder to "en.lproj", then re-added the
storyboard. After I did a build the warning
On 27 Mar 2015, at 12:55 pm, Scott Ribe wrote:
>
> Be warned, starting with Mavericks things went wacko-batshit stupid if the
> sheet is near the screen bounds...
My app is 10.9 and later only, but I think I'm mostly protected by virtue of a
minimum size for that splitview subview. (My use of
On Mar 26, 2015, at 7:08 PM, Shane Stanley wrote:
>
> FWIW, you can -- I do it. (Think of a deep-ish document window divided into
> top and bottom sections, and the user is doing stuff in the bottom part -- it
> makes more sense, it seems to me, to have the alert appear from the top of
> the b
On 27 Mar 2015, at 10:45 am, Quincey Morris
wrote:
>
> AFAIK custom sheet positioning is basically never done. (And I don’t know
> that you can force custom positioning on a NSAlert sheet.)
FWIW, you can -- I do it. (Think of a deep-ish document window divided into top
and bottom sections, an
On Mar 26, 2015, at 17:10 , Graham Cox wrote:
>
> One situation I think would be a suitable candidate for a custom-positioned
> alert (or popover) is when a text field fails validation. At the moment,
> there's little support for handling this gracefully - I think the default
> response is to
> On 2015/03/27, at 9:10, Graham Cox wrote:
>
>
>> On 27 Mar 2015, at 10:45 am, Quincey Morris
>> wrote:
>>
>> Without knowing more context, I’m not sure NSPopover is the right thing
>> either. If not, it probably ought to be some kind of custom NSPanel.
>
>
> One situation I think woul
> On 27 Mar 2015, at 10:45 am, Quincey Morris
> wrote:
>
> Without knowing more context, I’m not sure NSPopover is the right thing
> either. If not, it probably ought to be some kind of custom NSPanel.
One situation I think would be a suitable candidate for a custom-positioned
alert (or pop
On Mar 26, 2015, at 16:00 , Graham Cox wrote:
>
> Your requirement isn't clear - do you want a sheet to appear as if unattached
> to a host window, just floating in space? Even if you can achieve it, users
> will simply assume your app is buggy. Ideas like this are never seen in the
> wild for
Have you tried executing the script?
// Execute the script, compiling it first if it is not already compiled.
Return the result of executing the script, or nil and a pointer to an error
information dictionary for failure.
- (NSAppleEventDescriptor *)executeAndReturnError:(NSDictionary
**)errorInf
I think you might be able to use this:
[object performSelectorOnMainThread:(SEL)aSelector
withObject:nil
waitUntilDone:NO];
If I am interpreting the behavior of that call correctly, you would need
to call that once to get it started, then at the
> On 26 Mar 2015, at 10:57 pm, Dave wrote:
>
> i tried this just to get something working for now, but it doesn’t seem to
> affect where the Alert is displayed.
>
> myAlert = [NSAlert alertWithMessageText:@"Do you really want to do that?"
> defaultButton:@“No" alternateButton:@“Yes" otherButt
Hi,
I’m running the following Script from a Cocoa App using NSAppleScript:
set myWindowName to "Test 2"
set myNewSubject to "[High] Test 2"
tell application id "com.microsoft.Outlook"
activate
save front window
set myMessageList to current messages
set myMessage to
i tried this just to get something working for now, but it doesn’t seem to
affect where the Alert is displayed.
myAlert = [NSAlert alertWithMessageText:@"Do you really want to do that?"
defaultButton:@“No" alternateButton:@“Yes" otherButton:nil
informativeTextWithFormat:@"It might cause mayhem!
17 matches
Mail list logo
