On 1 Apr 2015, at 1:33 pm, Shane Stanley wrote:
>
> I'm sure I'm missing something simple, but it's escaping me.
Yep. Bindings.
--
Shane Stanley
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderat
I start a new project, then drag a text field with attached number formatter
into the window. I set the formatter's minimum to 0 and maximum to 1. I run,
then enter 3 and hit return. I get a beep, but no error dialog. Yet I have
existing projects where a dialog appears. I'm sure I'm missing some
Hello,
While attempting to submit my App for validation to iTunes Connect, I get a
“CFBundleIdentifier com.. not found". But when I check the
CFBundleIdentifier in my project’s Info.plist, it matches the very string the
validation error prompt says cannot be found. Could there be something else
It also depends on your window’s transparency settings, which you don’t always
control - Apple changed that on the window that holds the toolbar accessory in
fullscreen, changing my patterned grab zone into a bunch of tiny ungrabbable
holes :(
On Mar 31, 2015, at 2:53 PM, Eyal Redler wrote:
>
Thanks Uli, Using
NSRectFillUsingOperation( box, NSCompositeSourceAtop )
did the trick.
Thanks to all who answered. I've been developing for mac for over 20 years and
I find it really odd that I've never came across this behaviour.
Eyal
> On Mar 31, 2015, at 4:42 PM, Uli Kusterer
> wrote:
>
Dave wrote:
> I’m running the following Script from a Cocoa App using NSAppleScript:
For reference, some quick how-tos on calling AppleScript from ObjC/Python:
* using NSAppleScript class:
http://appscript.sourceforge.net/nsapplescript.html
* using AppleScriptObjC framework:
http://appscrip
> On Mar 24, 2015, at 8:44 PM, Daryle Walker wrote:
>
> A segment from my command-line tool:
>
>>NSURL * const finalLocation = [NSURL
>> fileURLWithPath:response.suggestedFilename isDirectory:NO];
>>
>>[[NSFileManager defaultManager] moveItemAtURL:location
>>
> On Mar 31, 2015, at 5:39 AM, Eyal Redler wrote:
>
> For some reason the view is showing through the windows/desktop behind the
> window where my view is located.
> Surly this is a manifestation of one of the (somewhat unwanted IMO) features
> of Yosemite
Nope, it’s always been that way. I r
> On 31 Mar 2015, at 15:59, Charles Jenkins wrote:
>
> I confused the view with the color, but in essence that’s what I was afraid
> you were saying: that Yosemite is blending with unrelated content instead of
> what is layered by your app/view/window/whatever “under” the rectangle you’re
> t
I confused the view with the color, but in essence that’s what I was afraid you
were saying: that Yosemite is blending with unrelated content instead of what
is layered by your app/view/window/whatever “under” the rectangle you’re trying
to fill.
I believe you should file a bug report on this.
> On 31 Mar 2015, at 14:39, Eyal Redler wrote:
> I'm working on a custom view. I'm using the following code to draw the view
>
> [[NSColor colorWithDeviceRed:(float)42/255
> green:(float)49/255
>
Whoops. Sorry to everyone about the doubled-up email. I had a problem with my
email program and thought the first reply didn’t send, so I tried again, and
apparently it went out as a reply to my own reply :-(
--
Charles
___
Cocoa-dev mailing list (C
Eyal,
I don’t have an answer for you, just a request for clarification. If a view has
a low alpha setting, you expect the content behind it to show through, so your
description sounds like normal behavior. However, I suspect you’re dealing with
a real problem.
Are you saying that your view wit
Hi,
I'm working on a custom view. I'm using the following code to draw the view
[[NSColor colorWithDeviceRed:(float)42/255
green:(float)49/255
blue:(float)58/255
14 matches
Mail list logo
