Re: Avoiding link conflicts with a static library

I’m basing this on rdar://problem/19209161 , which appears to still be open. I haven’t tried this myself. Saagar Jha > On Apr 5, 2018, at 18:06, Alex Zavatone wrote: > > >> On Apr 5, 2018, at 7:49 PM, Saagar Jha > > wrote: >> >> I think there used to be a bug (mi

Re: Avoiding link conflicts with a static library

> On Apr 5, 2018, at 7:49 PM, Saagar Jha wrote: > > I think there used to be a bug (might still be?) where Xcode didn’t > automatically strip out the x86 simulator slices when you were archiving. > > Saagar Jha When looking at the Archive scheme, it should use Release as the build config. R

Re: Avoiding link conflicts with a static library

I think there used to be a bug (might still be?) where Xcode didn’t automatically strip out the x86 simulator slices when you were archiving. Saagar Jha > On Apr 5, 2018, at 07:29, Alex Zavatone wrote: > > >> On Apr 5, 2018, at 4:19 AM, Redler Eyal wrote: >> > 2. (More importantly

Re: Avoiding link conflicts with a static library

You could weak link against OpenCV then dlopen it at runtime depending on whether it’s already loaded or not. As for packaging, I’d stick them both in a zip with a README telling them where to drag each thing in Xcode. Saagar Jha > On Apr 5, 2018, at 01:42, Redler Eyal wrote: > > We have

Re: runModalSession handling

On Apr 5, 2018, at 15:27 , Tom Doan wrote: > > I checked and none of my stopModalWithCodes are being fired, so the result > code has to be coming off the system dialog. I did a kludge where I used 100 > and 101 for my own stop codes, and continued on 0 and 1, and that seemed to > work around t

Re: problem getting CALayer to draw an image

Sorry about the mysterious blank posts. Let's see if I can do it with plain text rather than HTML. On 4/5/2018 11:05 AM, David Duncan wrote: >> On Apr 5, 2018, at 10:53 AM, James Walker wrote: >> >> I have a generic NSView that contains some subviews, and I'd like to add a background image

runModalSession handling

Based upon a recommendation that I found, I changed up code from running a modal dialog to use beginModalSessionForWindow and runModalSession. Unfortunately, if I run an NSOpenPanel from within this (used for a browse for a target directory), runModalSession for *my* dialog returns the 0 or 1

Re: Avoiding link conflicts with a static library

> On Apr 5, 2018, at 3:05 PM, Jim Adams wrote: > > We build ours using archive before lipo-ing and we don’t have to strip the > simulator bits out. My point was that when you distribute to clients, they will want to test using a simulator, but will want to ship without it. So, you’ll likely

Re: problem getting CALayer to draw an image (repost)

___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.co

Re: Avoiding link conflicts with a static library

We build ours using archive before lipo-ing and we don’t have to strip the simulator bits out. > On Apr 5, 2018, at 4:03 PM, Cody Garvin wrote: > > EXTERNAL > > We send them one that is lipod then give them a build phase script that > strips the opposite architecture out. A bit easier than sw

Re: Avoiding link conflicts with a static library

We send them one that is lipod then give them a build phase script that strips the opposite architecture out. A bit easier than switching frameworks that could potentially have different versions and avoid separate targets to add the different architecture library to. Let me know if you’d like o

Re: problem getting CALayer to draw an image

___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.co

Re: problem getting CALayer to draw an image

___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.co

Re: Avoiding link conflicts with a static library

> On Apr 5, 2018, at 1:37 PM, Redler Eyal wrote: > > >> On 5 Apr 2018, at 17:29, Alex Zavatone wrote: >> >> >>> On Apr 5, 2018, at 4:19 AM, Redler Eyal wrote: >>> > >> 2. (More importantly) It makes the client's binary larger since it will >> have to include our full library,

Re: Avoiding link conflicts with a static library

> On 5 Apr 2018, at 17:29, Alex Zavatone wrote: > > >> On Apr 5, 2018, at 4:19 AM, Redler Eyal wrote: >> > 2. (More importantly) It makes the client's binary larger since it will > have to include our full library, including simulator code. (correct me > if I'm wrong)

Re: problem getting CALayer to draw an image

> On Apr 5, 2018, at 10:53 AM, James Walker wrote: > > I have a generic NSView that contains some subviews, and I'd like to add a > background image. I tried code like this: > > NSImage* backgroundImage = [NSImage imageNamed: @"blueprint controls.png"]; > CALayer* holderLayer = [CALayer layer

Re: problem getting CALayer to draw an image

If you take out the setNeedsDisplay it draws ok. —Rob > On Apr 5, 2018, at 11:53 AM, James Walker wrote: > > I have a generic NSView that contains some subviews, and I'd like to add a > background image. I tried code like this: > > NSImage* backgroundImage = [NSImage imageNamed: @"blueprint

problem getting CALayer to draw an image

I have a generic NSView that contains some subviews, and I'd like to add a background image. I tried code like this: NSImage* backgroundImage = [NSImage imageNamed: @"blueprint controls.png"]; CALayer* holderLayer = [CALayer layer]; _throttleHolder.layer = holderLayer; _throttleHolder.wantsLaye

Re: UITabBarItem selection Voice over speaks number apart from accessibility label,value

Can you file a bug with a complete sample and report the bug# back to the list? It isn’t immediately obvious to me where the numbers you report are coming from, or why accessibility would speak them, but I can take a look once I have a sample in front of me. > On Apr 5, 2018, at 4:37 AM, Devars

Re: Avoiding link conflicts with a static library

> On Apr 5, 2018, at 4:19 AM, Redler Eyal wrote: > >>> 2. (More importantly) It makes the client's binary larger since it will have to include our full library, including simulator code. (correct me if I'm wrong) >>> >>> No, you should ask your client to remove the simulator s

UITabBarItem selection Voice over speaks number apart from accessibility label,value

I am programmatically assigning bar button items to UITabBar using below code: -(void)setupTabs { UIImage *icon1 = [[UIImage imageNamed:@"Icon1"] imageWithRenderingMode:UIImageRenderingModeAlwaysTemplate]; UITabBarItem *option1 = [[UITabBarItem alloc] initWithTitle:@"Option1" image: icon1

Re: Avoiding link conflicts with a static library

>> >>> 2. (More importantly) It makes the client's binary larger since it will >>> have to include our full library, including simulator code. (correct me if >>> I'm wrong) >> >> No, you should ask your client to remove the simulator slice before >> submitting to the App Store. > > This is co

Re: Avoiding link conflicts with a static library

> >>> No, you should ask your client to remove the simulator slice before >>> submitting to the App Store. >> >> I guess, but it would hurt the usage simplicity. Certainly compared to the >> current solution as a static library. > > Any app using Carthage already has to do this, so it's appare

Re: Avoiding link conflicts with a static library

We have two issues with the dynamic framework 1. It makes it easier to pirate our technology (having our stuff neatly packaged seperaterly) >>> >>> I may be misunderstanding you, but why does your code need to be separate? >>> Can’t you statically link against your framework, whic