Re: NSComboBox in the tab ring
Yep - I ended up going with a Pop Up Button for the reason's you've both mentioned. Thanks for replying with a bit of explanation and suggestions! -Luther On Wed, Oct 29, 2014 at 3:16 PM, Graham Cox graham@bigpond.com wrote: On 19 Oct 2014, at 3:14 pm, Luther Baker lutherba...@gmail.com wrote: I don't want to allow the user to type randomly into the text field It *is* a text field. Sounds like what you really want is a pop-up menu button. --Graham ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Closing window on Yosemite crashes (isFlipped)
Since Yosemite I have seen a lot of crash reports submitted where the crash is triggered by closing a window and it mostly ends with sending `isFlipped`, `_isLayerBacked`, or `transformRect:` to a wrong object. I have attached a sample crash report below. Does anyone else see this? Anyone know what could cause it? Any hints on what I could do to debug it? I haven’t been able to reproduce a similar crash in my own test environment, so any debugging would need to be done by deploying test builds with debug code. Application Specific Information: objc_msgSend() selector name: isFlipped Performing @selector(_close:) from sender _NSThemeCloseWidget 0x6119c560 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x7fff897530dd objc_msgSend + 29 1 com.apple.AppKit 0x7fff8afb7d79 -[NSView convertRect:toView:] + 212 2 com.apple.AppKit 0x7fff8b094b0e -[NSView(NSInternal) _updateLayerTreeRenderer] + 935 3 com.apple.AppKit 0x7fff8b1c1548 -[NSView(NSInternal) _pauseLayerTreeRenderer] + 144 4 com.apple.CoreFoundation 0x7fff830bacbc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12 5 com.apple.CoreFoundation 0x7fff82fac1b4 _CFXNotificationPost + 3140 6 com.apple.Foundation 0x7fff903acea1 -[NSNotificationCenter postNotificationName:object:userInfo:] + 66 7 com.apple.AppKit 0x7fff8b0c70f4 -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 4151 8 com.apple.AppKit 0x7fff8b0c5e17 -[NSWindow _doOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 829 9 com.apple.AppKit 0x7fff8b0c5a6b -[NSWindow orderWindow:relativeTo:] + 159 10 com.apple.AppKit 0x7fff8b1bf587 __18-[NSWindow _close]_block_invoke + 444 11 com.apple.AppKit 0x7fff8b1bf395 -[NSWindow _close] + 363 12 com.apple.AppKit 0x7fff8b1bf145 -[NSWindow __close] + 312 13 libsystem_trace.dylib0x7fff8fc41cd7 _os_activity_initiate + 75 14 com.apple.AppKit 0x7fff8b1765e7 -[NSApplication sendAction:to:from:] + 410 15 com.apple.AppKit 0x7fff8b176410 -[NSControl sendAction:to:] + 86 16 com.apple.AppKit 0x7fff8b34adaf __26-[NSCell _sendActionFrom:]_block_invoke + 131 17 libsystem_trace.dylib0x7fff8fc41cd7 _os_activity_initiate + 75 18 com.apple.AppKit 0x7fff8b1bef2c -[NSCell _sendActionFrom:] + 144 19 com.apple.AppKit 0x7fff8b331ab2 -[NSButtonCell _sendActionFrom:] + 39 20 libsystem_trace.dylib0x7fff8fc41cd7 _os_activity_initiate + 75 21 com.apple.AppKit 0x7fff8b1d9a66 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 2731 22 com.apple.AppKit 0x7fff8b1d8cc1 -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 491 23 com.apple.AppKit 0x7fff8b1d8289 -[NSControl mouseDown:] + 714 24 com.apple.AppKit 0x7fff8b660e5d -[_NSThemeWidget mouseDown:] + 315 25 com.apple.AppKit 0x7fff8b6d1fef -[NSWindow _reallySendEvent:] + 12827 26 com.apple.AppKit 0x7fff8b15c65c -[NSWindow sendEvent:] + 368 27 com.apple.AppKit 0x7fff8b10e1e6 -[NSApplication sendEvent:] + 2238 28 com.apple.AppKit 0x7fff8af9afe8 -[NSApplication run] + 711 29 com.apple.AppKit 0x7fff8af86424 NSApplicationMain + 1832 ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
NSSplitView divider tracking-area
in a panel, the tracking area for NSSplitView’s divider is only active if the panel is key, i.e. the cursor is not affected otherwise. as a panel is not generally key unless needed, ought not this area be always active? anyone agree? anyone have a workaround? thanks, edward ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
[MEET] Toronto CocoaHeads / tacow - November 12
tacow's next meeting is scheduled for 6:30 PM on Wednesday, November 12, 2014 in meeting room 310 of Metro Hall. Note that, because of Remembrance Day, this is a day later than our usual second-Tuesday schedule Marc Prud'hommeaux will be presenting Thinking in Swift: new paradigms for the Objective-C coder. For more details and to RSVP, head over to http://www.meetup.com/tacow-org/events/169610822/. Thanks, and hope to see you there! Karl Moskowski kmoskow...@me.com http://about.me/kolpanic ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Closing window on Yosemite crashes (isFlipped)
I haven’t encountered this myself. This is stream-of-consciousness, adding the presence of convertRect:toView: in the trace as the immediate caller… … The classic cause of a message arriving at the wrong object is that the expected object had been deallocated and its address recycled for the object that eventually got the bad call. The bad call comes of the calling object’s keeping an orphan pointer to the original. I’d think ARC would make that very rare, but maybe not impossible, especially if the orphan pointer were unsafe_unretained. It’s too bad you don’t have a reproducible case; if there were one, I’d use the Allocations and Leaks instruments, with Allocations set to record the complete malloc/retain/release/free life cycles. … It’s worse in that if it is an orphan pointer, it smells as if it was kept in the view hierarchy of a framework-managed object. … I wonder if _NSThemeCloseWidget is an NSCell; a cell wouldn’t implement any of those messages, assuming the subclass doesn’t add them. From the selectors you mention (plus the caller being inside convertRect:**toView:**), the caller seems to expect an NSView. — F On 30 Oct 2014, at 9:59 AM, Allan Odgaard lists+cocoa-...@simplit.com wrote: Since Yosemite I have seen a lot of crash reports submitted where the crash is triggered by closing a window and it mostly ends with sending `isFlipped`, `_isLayerBacked`, or `transformRect:` to a wrong object. Application Specific Information: objc_msgSend() selector name: isFlipped Performing @selector(_close:) from sender _NSThemeCloseWidget 0x6119c560 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x7fff897530dd objc_msgSend + 29 1 com.apple.AppKit 0x7fff8afb7d79 -[NSView convertRect:toView:] + 212 2 com.apple.AppKit 0x7fff8b094b0e -[NSView(NSInternal) _updateLayerTreeRenderer] + 935 3 com.apple.AppKit 0x7fff8b1c1548 -[NSView(NSInternal) _pauseLayerTreeRenderer] + 144 4 com.apple.CoreFoundation 0x7fff830bacbc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12 5 com.apple.CoreFoundation 0x7fff82fac1b4 _CFXNotificationPost + 3140 6 com.apple.Foundation 0x7fff903acea1 -[NSNotificationCenter postNotificationName:object:userInfo:] + 66 7 com.apple.AppKit 0x7fff8b0c70f4 -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 4151 8 com.apple.AppKit 0x7fff8b0c5e17 -[NSWindow _doOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 829 9 com.apple.AppKit 0x7fff8b0c5a6b -[NSWindow orderWindow:relativeTo:] + 159 10 com.apple.AppKit 0x7fff8b1bf587 __18-[NSWindow _close]_block_invoke + 444 11 com.apple.AppKit 0x7fff8b1bf395 -[NSWindow _close] + 363 12 com.apple.AppKit 0x7fff8b1bf145 -[NSWindow __close] + 312 13 libsystem_trace.dylib0x7fff8fc41cd7 _os_activity_initiate + 75 14 com.apple.AppKit 0x7fff8b1765e7 -[NSApplication sendAction:to:from:] + 410 15 com.apple.AppKit 0x7fff8b176410 -[NSControl sendAction:to:] + 86 16 com.apple.AppKit 0x7fff8b34adaf __26-[NSCell _sendActionFrom:]_block_invoke + 131 17 libsystem_trace.dylib0x7fff8fc41cd7 _os_activity_initiate + 75 18 com.apple.AppKit 0x7fff8b1bef2c -[NSCell _sendActionFrom:] + 144 19 com.apple.AppKit 0x7fff8b331ab2 -[NSButtonCell _sendActionFrom:] + 39 20 libsystem_trace.dylib0x7fff8fc41cd7 ... ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: NSSplitView divider tracking-area
in a panel, the tracking area for NSSplitView’s divider is only active if the panel is key, i.e. the cursor is not affected otherwise. as a panel is not generally key unless needed, ought not this area be always active? anyone agree? anyone have a workaround? What does a panel mean to you? AFAIK the tracking area of the split view is not affected by anything in the way you describe, and looking at the disassembly shows nothing out of the ordinary. The delegate has the ability to add to the area, but that's it. -- Seth Willits ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: NSSplitView divider tracking-area
On Oct 30, 2014, at 12:34 PM, Seth Willits sli...@araelium.com wrote: in a panel, the tracking area for NSSplitView’s divider is only active if the panel is key, i.e. the cursor is not affected otherwise. as a panel is not generally key unless needed, ought not this area be always active? anyone agree? anyone have a workaround? What does a panel mean to you? an NSPanel AFAIK the tracking area of the split view is not affected by anything in the way you describe, and looking at the disassembly shows nothing out of the ordinary. The delegate has the ability to add to the area, but that's it. i’m not sure what you mean—i have verified: if the NSPanel is key when mousing over the divider, the cursor changes to a resize cursor, as expected; if not key the cursor is unaffected. -- Seth Willits ___ 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.com/mailman/options/cocoa-dev/etaffel%40me.com This email sent to etaf...@me.com ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
When I rotate the MKMapView with transform, setCenter not working.
Hi all,
I rotate the MKMapView with setting the rotation transform. When I use
setCenter method to change the center coordinate of the map, the location of
this coordinate not in the center. Does anyone know what happened, and how to
solve this problem? Below is the code snipt.
- (void)viewDidLoad {
[super viewDidLoad];
// Do any additional setup after loading the view, typically from a nib.
static CLLocationCoordinate2D aircraftCoordinate = {22.531474, 113.943516};
CGFloat width = self.view.bounds.size.width;
CGFloat height = self.view.bounds.size.height;
CGFloat newSize = sqrt(width* width + height * height);
UIView *tmpView = [[UIView alloc] initWithFrame:CGRectMake(0, 0, width,
height)];
[self.view insertSubview:tmpView atIndex:0];
self.containorView = tmpView;
MKMapView *tmpMapView = [[MKMapView alloc] initWithFrame:CGRectMake(0, 0,
newSize, newSize)];
[self.containorView addSubview:tmpMapView];
self.mapView = tmpMapView;
[tmpMapView setCenter:self.containorView.center];
self.annotation = [[DJITestAnnotation alloc] init];
_annotation.coordinate = aircraftCoordinate;
[self.mapView addAnnotation:self.annotation];
self.mapView.delegate = self;
[self.mapView setTransform:CGAffineTransformMakeRotation(90 * M_PI_4 /
180)];
}
- (IBAction)location:(id)sender {
self.mapView.camera.centerCoordinate = _annotation.coordinate;
}
Best Regards,
Sunny Lee
___
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.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Can an use introspection to determine if its a production app from the App Store?
Can an iOS app examine some property to determine if its been installed as a development style app (ie Test Flight, or Xcode, etc), or was installed via the App Store. [I support a library where the app is suppose to pass a flag, but clients are making errors...] David ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: NSSplitView divider tracking-area
On Oct 30, 2014, at 10:45 AM, edward taffel etaf...@me.com wrote: AFAIK the tracking area of the split view is not affected by anything in the way you describe, and looking at the disassembly shows nothing out of the ordinary. The delegate has the ability to add to the area, but that's it. i’m not sure what you mean—i have verified: if the NSPanel is key when mousing over the divider, the cursor changes to a resize cursor, as expected; if not key the cursor is unaffected. A tracking area can choose when to track, and it appears that NSSplitView has chosen to track only when the window is key. You may be able to access the tracking area via the -trackingAreas method and swap it out with one of your own creation, but that is pretty hacky and probably volatile. HTH, Keary Suska Esoteritech, Inc. Demystifying technology for your home or business ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Can an use introspection to determine if its a production app from the App Store?
The following seems to work from experimentation... For an application installed through TestFlight Beta the receipt file is named StoreKit\sandboxReceipt vs the usual StoreKit\receipt. Using [NSBundle appStoreReceiptURL] you can look for sandboxReceipt at the end of the URL. NSURL *receiptURL = [[NSBundle mainBundle] appStoreReceiptURL]; NSString *receiptURLString = [receiptURL path]; BOOL isRunningTestFlightBeta = ([receiptURLString rangeOfString:@sandboxReceipt].location != NSNotFound); sandboxReceipt is also the name of the receipt file when running builds locally. On Thu, Oct 30, 2014 at 10:38 AM, David Hoerl dho...@mac.com wrote: Can an iOS app examine some property to determine if its been installed as a development style app (ie Test Flight, or Xcode, etc), or was installed via the App Store. [I support a library where the app is suppose to pass a flag, but clients are making errors...] David ___ 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.com/mailman/options/cocoa-dev/websites%40paperetto.com This email sent to websi...@paperetto.com -- David Brittain da...@paperetto.com ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
AppDefined events getting lost; 10.10 only
Dear experts, I’m encountering a serious (to me) problem in Yosemite where events are sent to the event queue of my application, but never received. I’m posting events of type NSApplicationDefined using [NSApp postEvent:atStart:]. Normally, these are received in a run loop, which uses the events to terminate and do something else. Because it does not terminate, the application becomes unresponsive. This worked fine prior to 10.10, and it normally works fine in 10.10, except when a user causes several (other) events to be added to the queue in rapid succession. Double-clicking a toolbar icon reliably reproduces the problem. Testing my code, I made sure I numbered and logged every one of those AppDefined events going in. I also log every event seen by the NSApplication’s sendEvent function. After the rapid inputs take place, those AppDefined events clearly are no longer received. The occurs whether I implement my own “run” function or use the default one. I made sure that there is no other call to “run” or “nextEventMatchingMask:untilDate:..” in the application. A workaround setting a timeout with the untilDate argument to nextEventMatchingMask addresses the issue temporarily. I’m told by users that the problem started in a Yosemite pre-release version, halfway through the public test phase. Is there any other way in Cocoa to clear the event loop or to receive events? Can you think of any potential actions in my code that could cause this, as opposed to a bug in 10.10? Thanks, David To reproduce: download binary or source code from: https://github.com/davidswelt/aquamacs-emacs/releases/tag/Aquamacs-3.1a Start up, then double-click the “search” icon. Event loop is in [EmacsApp run] method in nsterm.m:4774. This loop does not exit because the marker event isn’t retrieved. Event is sent in ns_send_appdefined(), nsterm.m:3647 Events of this type are received in sendEvent: in nsterm.m:4805. ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: NSSplitView divider tracking-area
On Oct 30, 2014, at 1:42 PM, Keary Suska cocoa-...@esoteritech.com wrote: A tracking area can choose when to track, and it appears that NSSplitView has chosen to track only when the window is key. You may be able to access the tracking area via the -trackingAreas method and swap it out with one of your own creation, but that is pretty hacky and probably volatile. i agree! do you feel it should always track? [anyone else?] only, these days i’m loath to write this type of report without weight of consensus. HTH, ofc, very great help. thanks for your reply, edward Keary Suska Esoteritech, Inc. Demystifying technology for your home or business ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Can an use introspection to determine if its a production app from the App Store?
You could also inspect the provisioning profile: https://github.com/tcurdt/TCMobileProvision cheers, Torsten On Thu, Oct 30, 2014 at 6:44 PM, David Brittain websi...@paperetto.com wrote: The following seems to work from experimentation... For an application installed through TestFlight Beta the receipt file is named StoreKit\sandboxReceipt vs the usual StoreKit\receipt. Using [NSBundle appStoreReceiptURL] you can look for sandboxReceipt at the end of the URL. NSURL *receiptURL = [[NSBundle mainBundle] appStoreReceiptURL]; NSString *receiptURLString = [receiptURL path]; BOOL isRunningTestFlightBeta = ([receiptURLString rangeOfString:@sandboxReceipt].location != NSNotFound); sandboxReceipt is also the name of the receipt file when running builds locally. On Thu, Oct 30, 2014 at 10:38 AM, David Hoerl dho...@mac.com wrote: Can an iOS app examine some property to determine if its been installed as a development style app (ie Test Flight, or Xcode, etc), or was installed via the App Store. [I support a library where the app is suppose to pass a flag, but clients are making errors...] David ___ 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.com/mailman/options/cocoa-dev/websites%40paperetto.com This email sent to websi...@paperetto.com -- David Brittain da...@paperetto.com ___ 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.com/mailman/options/cocoa-dev/tcurdt%40vafer.org This email sent to tcu...@vafer.org ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Can an use introspection to determine if its a production app from the App Store?
Looks great, but I cannot read Objective C anymore - where is the Swift version??? On 10/30/14, 2:28 PM, Torsten Curdt wrote: You could also inspect the provisioning profile: https://github.com/tcurdt/TCMobileProvision cheers, Torsten On Thu, Oct 30, 2014 at 6:44 PM, David Brittain websi...@paperetto.com mailto:websi...@paperetto.com wrote: The following seems to work from experimentation... For an application installed through TestFlight Beta the receipt file is named StoreKit\sandboxReceipt vs the usual StoreKit\receipt. Using [NSBundle appStoreReceiptURL] you can look for sandboxReceipt at the end of the URL. NSURL *receiptURL = [[NSBundle mainBundle] appStoreReceiptURL]; NSString *receiptURLString = [receiptURL path]; BOOL isRunningTestFlightBeta = ([receiptURLString rangeOfString:@sandboxReceipt].location != NSNotFound); sandboxReceipt is also the name of the receipt file when running builds locally. On Thu, Oct 30, 2014 at 10:38 AM, David Hoerl dho...@mac.com mailto:dho...@mac.com wrote: Can an iOS app examine some property to determine if its been installed as a development style app (ie Test Flight, or Xcode, etc), or was installed via the App Store. [I support a library where the app is suppose to pass a flag, but clients are making errors...] David ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com mailto: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 http://lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/websites%40paperetto.com This email sent to websi...@paperetto.com mailto:websi...@paperetto.com -- David Brittain da...@paperetto.com mailto:da...@paperetto.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com mailto: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 http://lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/tcurdt%40vafer.org This email sent to tcu...@vafer.org mailto:tcu...@vafer.org ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
How make image nonvibrant in Yosemite NSVisualEffectView
I am trying to make my application's window behave like the Application Switcher behaves in Yosemite (open Application Switcher by pressing Command-Tab). There is one behavior I can't figure out. The Application Switcher's window background is vibrant, and so is the darker rectangle that marks the application to be made active, but the icon images are not vibrant. In my application, I can make the window background and the darker selection rectangle vibrant, but the icon image is vibrant, too. That is, blurred images and colors behind my window show through the icon image, as well as showing through the window background and the selection rectangle. From the limited discussion in the AppKit Release Note and the WWWDC 220 video, I gather that I could accomplish this by setting the NSVisualEffectView's maskImage property to encompass everything in my window except the icon image, but I have no idea how to create an inverse mask image. If you're curious about what kind of application would do this, I am updating my Applidude application for Yosemite: http://pfiddlesoft.com/pfiddles. -- Bill Cheeseman - b...@cheeseman.name ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: NSSplitView divider tracking-area
On Oct 30, 2014, at 11:19 , edward taffel etaf...@me.com wrote: i agree! do you feel it should always track? [anyone else?] There’s an argument that says it should change the cursor if and only if mouse down while the cursor is changed would “grab” the splitter. (So that would be a “yes” in your scenario, wouldn’t it? Does it grab the splitter anyway?) But there’s *also* a potential argument that says it should *not* change if the window containing the splitter is inactive, even if mouse down would grab the splitter, to avoid capturing the user’s attention when the mouse pointer happens to move over the splitter on its way to something else. (So that might be a “no” in your scenario, except…) If you see any value in that argument, then there’s also a potential question of what constitutes an inactive window (for this purpose). Does it need to be main to be active? Key? Any window in the active app? (So that might be a “yes” or a “no” in your scenario.) Finally, FWIW, I’ve encountered many situations in regular windows in many apps — when key-ness is not a factor AFAICT — where the cursor just doesn’t change when hovering over the splitter. Grabbing the splitter “fixes” the problem, in the sense that the cursor usually changes properly after releasing it, until the next time it happens. So there might be some non-intentional flakiness in the cursor tracking that just happens to be repeatable in the case you’ve described. Because of all that, I’d say it’s well worth a bug report to ask for clarification. ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: How make image nonvibrant in Yosemite NSVisualEffectView
On Oct 30, 2014, at 12:00 , Bill Cheeseman wjcheese...@gmail.com wrote: There is one behavior I can't figure out. The Application Switcher's window background is vibrant, and so is the darker rectangle that marks the application to be made active, but the icon images are not vibrant. In my application, I can make the window background and the darker selection rectangle vibrant, but the icon image is vibrant, too. That is, blurred images and colors behind my window show through the icon image, as well as showing through the window background and the selection rectangle. Maybe this is too simplistic, but isn’t there a solution where the icons are subviews of another view that has vibrancy turned off, not directly of the window content view? Or, in the worst case, a two-window solution where the icons are in a non-vibrant window positioned over the vibrant background window? From the limited discussion in the AppKit Release Note and the WWWDC 220 video, I gather that I could accomplish this by setting the NSVisualEffectView's maskImage property to encompass everything in my window except the icon image, but I have no idea how to create an inverse mask image. Because … it’s an issue of creating masks generally, or of getting icon-shaped bitmaps in particular? ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: NSSplitView divider tracking-area
On Oct 30, 2014, at 3:19 PM, Quincey Morris quinceymor...@rivergatesoftware.com wrote: On Oct 30, 2014, at 11:19 , edward taffel etaf...@me.com mailto:etaf...@me.com wrote: i agree! do you feel it should always track? [anyone else?] There’s an argument that says it should change the cursor if and only if mouse down while the cursor is changed would “grab” the splitter. (So that would be a “yes” in your scenario, wouldn’t it? Does it grab the splitter anyway?) yes, works fine. But there’s *also* a potential argument that says it should *not* change if the window containing the splitter is inactive, even if mouse down would grab the splitter, to avoid capturing the user’s attention when the mouse pointer happens to move over the splitter on its way to something else. (So that might be a “no” in your scenario, except…) then it’s a rollover. If you see any value in that argument, then there’s also a potential question of what constitutes an inactive window (for this purpose). Does it need to be main to be active? Key? Any window in the active app? (So that might be a “yes” or a “no” in your scenario.) an open document, if any, is main. panels float are active; they may be key but not main. so, yes—i think the rollover should be active in this context. Finally, FWIW, I’ve encountered many situations in regular windows in many apps — when key-ness is not a factor AFAICT — where the cursor just doesn’t change when hovering over the splitter. Grabbing the splitter “fixes” the problem, in the sense that the cursor usually changes properly after releasing it, until the next time it happens. So there might be some non-intentional flakiness in the cursor tracking that just happens to be repeatable in the case you’ve described. true— i might just leave it. Because of all that, I’d say it’s well worth a bug report to ask for clarification. if several NSSplitView users concur it’s a bug, i’ll write it ; otherwise, it’s just another enhancement request— the likelihood for action is small. thanks for your comments! ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: How make image nonvibrant in Yosemite NSVisualEffectView
On Oct 30, 2014, at 3:28 PM, Quincey Morris quinceymor...@rivergatesoftware.com wrote: Maybe this is too simplistic, but isn’t there a solution where the icons are subviews of another view that has vibrancy turned off, not directly of the window content view? Or, in the worst case, a two-window solution where the icons are in a non-vibrant window positioned over the vibrant background window? The problem is that using a nonvibrant subview or window yields a nonvibrant area that is in the shape of a rectangle. The Appkit Release Note discusses techniques like those you suggest, but it expressly calls out the limitation to rectangular effects. What I want is a nonvibrant image with an irregular shape, namely, the shape of the nontransparent parts of any application icon. Apple does that in Yosemite's Application Switcher. I'm going to go ahead a use the rectangular approach for now, because there is a wide border area of my window around the icon which will still show vibrancy. But I would like to find a way to do it like Application Switcher. Because … it’s an issue of creating masks generally, or of getting icon-shaped bitmaps in particular? My images are application icons obtained using -[NSWorkspace iconForFile:]. Like most application icons, they usually have irregularly shaped nontransparent areas. I want to create a rectangular mask with a hole in it, where the hole is in the shape of the nontransparent areas of the icon. Ideally a 1-bit mask. Assigning the mask to NSVisualEffectView's maskImage property will allow everything covered by the rectangular mask (namely the whole window) to show vibrancy, except that the area in the hole (namely, the icon shape) will not show vibrancy. At least, that's how I understand the discussion of maskImage in the AppKit Release Note or the WWDC 220 video. (I have already applied a rectangular maskImage with rounded corners, and it removes the square corners from the NSVisualEffectView perfectly.) -- Bill Cheeseman - b...@cheeseman.name ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: How make image nonvibrant in Yosemite NSVisualEffectView
On Oct 30, 2014, at 12:00 PM, Bill Cheeseman wjcheese...@gmail.com wrote: I am trying to make my application's window behave like the Application Switcher behaves in Yosemite (open Application Switcher by pressing Command-Tab). There is one behavior I can't figure out. The Application Switcher's window background is vibrant, and so is the darker rectangle that marks the application to be made active, but the icon images are not vibrant. In my application, I can make the window background and the darker selection rectangle vibrant, but the icon image is vibrant, too. That is, blurred images and colors behind my window show through the icon image, as well as showing through the window background and the selection rectangle. From the limited discussion in the AppKit Release Note and the WWWDC 220 video, I gather that I could accomplish this by setting the NSVisualEffectView's maskImage property to encompass everything in my window except the icon image, but I have no idea how to create an inverse mask image. The view hierarchy should look something like this: Blur Vibrant Background Icon View Icon View Icon View... Then you just move your single vibrant background as necessary to be behind the right icon view. It sounds like you are putting the icon view inside the vibrant background. -- David Duncan ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: How make image nonvibrant in Yosemite NSVisualEffectView
On Oct 30, 2014, at 4:04 PM, David Duncan david.dun...@apple.com wrote: Then you just move your single vibrant background as necessary to be behind the right icon view. It sounds like you are putting the icon view inside the vibrant background. According to the AppKit Release Note, at least as I understand it, vibrancy only works if the NSVisualEffectView comes first and views that are to be vibrant are made containment subviews of NSVisualEffectView. That is, every view in front of the NSVisualEffectView is automatically made vibrant. It stands to reason that any view that is placed behind the NSVisualEffectView will not be vibrant. My window content's background colors -- everything except the nontransparent portions of the icon image -- must be vibrant. To accomplish that, I make the NSVisualEffectView the window's contentView, and I insert a view that I call bubbleView as a subview of NSVisualEffectView. bubbleView contains the background colors. That way, NSVisualEffectView lies behind the background colors, and the background colors become vibrant as promised by the Release Note. So far, so good. I then put the icon image into bubbleView, precisely because I want the background colors that show through the transparent areas of the icon image to be vibrant. In other words, I don't want a rectangular area of background colors surrounding the icon image to be nonvibrant. Unfortunately, putting the icon image in bubbleview, in front of NSVisualEffectView, makes the nontransparent areas of the icon image vibrant, too, and I don't want that to happen. Are you suggesting that I should create another view -- call it iconView -- give it a transparent background color, put the icon image in it, make it the contentView of the window, and then make NSVisualEffectView a subview of iconView? Then bubbleView (without the icon image) could remain a subview of NSVisualEffectView so that bubbleView's background colors would be vibrant, as I require, or maybe I could just give NSVisualEffectView itself the background colors and dispense with bubbleView. Then the icon image would not be vibrant because it is not in front of NSVisualEffectView and is therefore outside of its influence. What I'm not sure of is how I will prevent the background colors in bubbleView or NSVisualEffectView from obscuring the icon image in iconView behind them. After all, they are supposed to be background colors lying behind the icon image, not foreground colors in front of it. It seems to me that doing it my way with a rectangular maskImage the size of the window, but containing a hole in the shape of the nontransparent parts of the icon image to block the vibrancy effects, is more in keeping with the way vibrancy is designed, and more likely to work. But I don't know how to create the hole in the right shape. I am researching CGImageRef routines that supposedly can do it. -- Bill Cheeseman - b...@cheeseman.name ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: How make image nonvibrant in Yosemite NSVisualEffectView
On Oct 30, 2014, at 12:56 PM, Bill Cheeseman wjcheese...@gmail.com wrote: My images are application icons obtained using -[NSWorkspace iconForFile:]. Like most application icons, they usually have irregularly shaped nontransparent areas. I want to create a rectangular mask with a hole in it, where the hole is in the shape of the nontransparent areas of the icon. Ideally a 1-bit mask. Assigning the mask to NSVisualEffectView's maskImage property will allow everything covered by the rectangular mask (namely the whole window) to show vibrancy, except that the area in the hole (namely, the icon shape) will not show vibrancy. At least, that's how I understand the discussion of maskImage in the AppKit Release Note or the WWDC 220 video. (I have already applied a rectangular maskImage with rounded corners, and it removes the square corners from the NSVisualEffectView perfectly.) One approach you might try is to attach a child window that draws the icons themselves on a transparent background, and doesn’t use an NSVisualEffectView. The parent would would still use an NSVEV and would get the vibrant effect, but the icons in the child window wouldn’t be vibrant. -eric ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: How make image nonvibrant in Yosemite NSVisualEffectView
On Oct 30, 2014, at 2:09 PM, Bill Cheeseman wjcheese...@gmail.com wrote: On Oct 30, 2014, at 4:04 PM, David Duncan david.dun...@apple.com wrote: Then you just move your single vibrant background as necessary to be behind the right icon view. It sounds like you are putting the icon view inside the vibrant background. According to the AppKit Release Note, at least as I understand it, vibrancy only works if the NSVisualEffectView comes first and views that are to be vibrant are made containment subviews of NSVisualEffectView. That is, every view in front of the NSVisualEffectView is automatically made vibrant. Every view (and its subviews) contained in an NSVisualEffectView that returns YES from allowsVibrancy is made vibrant. If a given view returns NO from allowsVibrant, and none of its superviews returns YES, than that view will not be vibrant. It stands to reason that any view that is placed behind the NSVisualEffectView will not be vibrant. My window content's background colors -- everything except the nontransparent portions of the icon image -- must be vibrant. To accomplish that, I make the NSVisualEffectView the window's contentView, and I insert a view that I call bubbleView as a subview of NSVisualEffectView. bubbleView contains the background colors. That way, NSVisualEffectView lies behind the background colors, and the background colors become vibrant as promised by the Release Note. So far, so good. I then put the icon image into bubbleView And that is where you go off the rails. That icon image cannot be a subview of a view that returns YES from allowsVibrancy if you want it to not be vibrant. But it can be a subview of the NSVisualEffectView. , precisely because I want the background colors that show through the transparent areas of the icon image to be vibrant. In other words, I don't want a rectangular area of background colors surrounding the icon image to be nonvibrant. Unfortunately, putting the icon image in bubbleview, in front of NSVisualEffectView, makes the nontransparent areas of the icon image vibrant, too, and I don't want that to happen. If you position the icon view such that it is rendered in the same position, but not in the same hierarchy as the view hierarchy that does allow vibrancy, you should get what you are looking for. The transparent regions of the icon will show the vibrancy (because the view draws over) without the non-transperant regions turning vibrant. Are you suggesting that I should create another view -- call it iconView -- give it a transparent background color, put the icon image in it, make it the contentView of the window, and then make NSVisualEffectView a subview of iconView? Then bubbleView (without the icon image) could remain a subview of NSVisualEffectView so that bubbleView's background colors would be vibrant, as I require, or maybe I could just give NSVisualEffectView itself the background colors and dispense with bubbleView. Then the icon image would not be vibrant because it is not in front of NSVisualEffectView and is therefore outside of its influence. What I'm not sure of is how I will prevent the background colors in bubbleView or NSVisualEffectView from obscuring the icon image in iconView behind them. After all, they are supposed to be background colors lying behind the icon image, not foreground colors in front of it. It seems to me that doing it my way with a rectangular maskImage the size of the window, but containing a hole in the shape of the nontransparent parts of the icon image to block the vibrancy effects, is more in keeping with the way vibrancy is designed, and more likely to work. But I don't know how to create the hole in the right shape. I am researching CGImageRef routines that supposedly can do it. -- Bill Cheeseman - b...@cheeseman.name ___ 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.com/mailman/options/cocoa-dev/david.duncan%40apple.com This email sent to david.dun...@apple.com -- David Duncan ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Can an use introspection to determine if its a production app from the App Store?
On 31 Oct 2014, at 5:38 am, David Hoerl dho...@mac.com wrote: Looks great, but I cannot read Objective C anymore - where is the Swift version??? Obj-C isn't going anywhere soon, and Swift isn't yet ready for hardcore commercial use. I can't see the transition taking any less than five years, so what are you going to do in that time? Just twiddle your thumbs, or get on with building your apps? --Graham ___ 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.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
