On Mar 3, 2013, at 9:18 PM, Kyle Sluder wrote:
> On Mar 3, 2013, at 4:13 PM, "Rick C." wrote:
>
>> @Rob - yes I'm able to reproduce it. Still an issue running all the
>> latest...
>> @Jerry - yes I think it's directly related to transforming the app.
>> Unfortunately I really want this beha
On Mar 3, 2013, at 4:13 PM, "Rick C." wrote:
> @Rob - yes I'm able to reproduce it. Still an issue running all the latest...
> @Jerry - yes I think it's directly related to transforming the app.
> Unfortunately I really want this behavior in my app so removing it creates
> other issues :-)
W
@Rob - yes I'm able to reproduce it. Still an issue running all the latest...
@Jerry - yes I think it's directly related to transforming the app.
Unfortunately I really want this behavior in my app so removing it creates
other issues :-)
On Mar 4, 2013, at 7:08 AM, Jerry Krinock wrote:
>
>
On 2013 Feb 28, at 15:22, Rick C. wrote:
> You're having the same issue? FWIW I moved it to
> applicationWillFinishLaunching and changed it to NSApplication activation
> policy and I see no difference in the behavior.
I think that transforming to a foreground process is likely an important
On Feb 28, 2013, at 6:22 PM, Rick C. wrote:
> You're having the same issue? FWIW I moved it to
> applicationWillFinishLaunching and changed it to NSApplication activation
> policy and I see no difference in the behavior…
So you are able to reproduce it? Any tips? I’ve tried everything I can t
You're having the same issue? FWIW I moved it to
applicationWillFinishLaunching and changed it to NSApplication activation
policy and I see no difference in the behavior...
On Feb 28, 2013, at 9:55 PM, Rob McBroom wrote:
> On Feb 27, 2013, at 9:02 PM, Rick C. wrote:
>
>> I have users stil
On Feb 27, 2013, at 9:02 PM, Rick C. wrote:
> I have users still reporting this to me on 10.8.2. I am calling
> kProcessTransformToForegroundApplication in initialize maybe this is my
> problem?
We’re calling it in `init`. I’ll try moving it to
`applicationWillFinishLaunching`. Stabbing in t
I have users still reporting this to me on 10.8.2. I am calling
kProcessTransformToForegroundApplication in initialize maybe this is my problem?
On Feb 28, 2013, at 9:48 AM, Seth Willits wrote:
>
> Yeah, there's nothing you can do about it (and as I recall it wasn't a big
> deal anyway). W
Yeah, there's nothing you can do about it (and as I recall it wasn't a big deal
anyway). When I first heard about it, it was right around 10.7.0 so it was
users either on 10.6 or early 10.7. I haven't heard a user complain about it in
a long time, so it was probably fixed somewhere in later 10.
Yes that's it! So if there's no solution for now I guess I'm stuck... :-(
And to answer previous questions yes both icons point to the same location...
On Feb 28, 2013, at 8:20 AM, Seth Willits wrote:
>
> For what it's worth, I'm certain there's a bug in some versions of OS X where
> apps
For what it's worth, I'm certain there's a bug in some versions of OS X where
apps that transform from background to foreground processes
("TransformProcessType" or the newer NSApplication activation policy) would
cause the Dock to show two icons. I'm pretty sure I filed a radar for it a long
A shot in the dark but will this solve the problem? kills lsregister.
http://underurhat.com/tips-tricks/os-x-lion-how-to-fix-the-duplicate-application-bug-in-open-with-menu/
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post ad
On Feb 27, 2013, at 3:45 AM, Stephane Sudre wrote:
> On Wed, Feb 27, 2013 at 9:27 AM, Rick C. wrote:
>> Hi,
>>
>> When a customer adds my app to Login Items in System Preferences it
>> (sometimes) causes my app to launch showing 2 icons in the dock after a
>> restart. Only one instance is ru
On Wed, Feb 27, 2013 at 9:27 AM, Rick C. wrote:
> Hi,
>
> When a customer adds my app to Login Items in System Preferences it
> (sometimes) causes my app to launch showing 2 icons in the dock after a
> restart. Only one instance is running (Activity Monitor) and only one icon
> shows in Comman
14 matches
Mail list logo
