NSCollectionView transparent background
Is it possible to get NSCollectionView to render with a transparent background ? I've tried setting the backgroundColors array to clearColor, subclassing and filling in drawRect with clearColor, making sure the enclosing scroll view is not drawing its background and combinations of these all to no avail. Various combinations either result in the default white background or the black that looks like an opaque context that is being filled with clearColor Is there something I am missing or does this class just have some limitation here? FWIW I'm doing this on 10.10 with xcode 6.1 and no layers or visual effects views. ___ 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: dismissViewControllerAnimated bug in ios 8
On 26 Sep 2014, at 23:08, Herman Chan herman...@gmail.com wrote: Hi all, My set up is this. 1. present a view controller by calling presentViewController 2. in the presented view controller (modal), I create a UITextView and set it to be first responder when view has appeared. 3. set up the leftbarNavItem to call dismissViewControllerAnimated (at this moment the keyboard is raised). 4. click on the left bar button and the modal view dismissed, but the keyboard does not until a second later. Here is a sample project I have on github, please take a look: https://github.com/hermanccw/DismissBug Anyone run into this problem on iOS 8? I tested this same project on iOS 7 and it is fine. I have the same issue. But I suspect it’s somewhat deliberate on Apple’s part. The view problem now doesn’t resign first responder status until it’s actually offscreen. Fortunately there’s a pretty simple workaround: before dismissing the VC, force its views to end editing. That’ll kick off keyboard dismissal at the same time. ___ 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: Crash while resizing window
Am 24.09.2014 um 18:57 schrieb Alex Zavatone z...@mac.com: Stupid question, but is r ins or your variables? When the assertion is thrown, what is r? The debugger doesn't know anything about 'r'. There is a report on this on forums.codeblocks.org. Google for cgregion.c. There is a suggestion to go to Settings - Editor - Code Completion - Symbols Browser - Disable Symbols Browser. If I understand correctly, Code::Blocks, that is the IDE of that name, has a bug that hits the same assertion and can be avoided by disabling the symbols browser of that IDE. I'm not using Code::Blocks and there is no 'Settings' menu item in Xcode. But thanks for the suggestion. Andreas ___ 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: Crash while resizing window
On 25 Sep 2014, at 2:44 am, Andreas Mayer andr...@harmless.de wrote: So ... something to do with some affine transform? Yes, I'm using affine transforms to rotate the window contents, which is located in a CALayer. A common cause of CG assertions on transforms is a 'Nan' or 'inf' value ending up in the transform (these may not be discovered until some funciton is called that uses the transform). This is pretty easy to cause, for example dividing by zero, by setting a scale of 0 in a transform. You really want to avoid this by sanitising parameters used to calculate transforms. Even having something apparently innocuous such as view frame rect of NSZeroRect can eventually cause a bad transform to be computed. That would be the sort of thing I'd be looking for here. --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
Re: Crash while resizing window
Am 29.09.2014 um 02:22 schrieb Graham Cox graham@bigpond.com: A common cause of CG assertions on transforms is a 'Nan' or 'inf' value ending up in the transform (these may not be discovered until some funciton is called that uses the transform). I just checked. The only parameter that's changing while rotating is the angle; and logging it, it seems perfectly fine. But now I noticed that it seems to depend on the CIFilter that is attached to the layer. Specifically, it is the Sepia filter that crashes. Other filters exhibit odd behavior, like ever more pixellated output. Are there documented limitations in respect to CIFilters and transforms? I'll try to detach the filter while rotating. But that seems an odd thing to have to do. Agh. Now I get the same assertion on re-applying the filter. It feels like I'm screwing up something basic. I just have no idea what. :-( Andreas ___ 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
Showing keyboard on SKScene - Swift
I am trying to show keyboard over an SKScene, I followed below steps: 1. Created a subclass of UIView - KeyboardDummyView 2. Implemented protocol UIKeyInput in it 3. Added a subview to GameViewController 4. Changed class of subview added to KeyboardDummyView For some reasons it is not working as expected, here is the sample code: https://github.com/Daemon-Devarshi/KeyboardOverSKScene Kindly suggest if I am doing anything wrong? Thanks, Devarshi ___ 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
-[NSTabView mouseDown:] blows stack in Yosemite SDK
I’m probably going to be on my own with this, but just in case anyone else has
seen anything like it or has any ideas…
OS X app, builds and runs fine in 10.9 or 10.10, when built with the 10.9 SDK.
But when I set the project’s SDK build setting to “Latest OS X (10.10)”, build,
run, and click anywhere in a document window (that contains a tab view), the
blows its stack. See call stack below, prior to which I had clicked in the
title bar.
Any ideas or similar experiences, let us know. Possibly this is related to the
addition of NSTabViewController in 10.10.
Jerry Krinock
…
#130958 0x7fff96f9ad70 in forwardMethod ()
#130959 0x7fff96f9ad70 in forwardMethod ()
#130960 0x7fff974074ea in -[NSTabView mouseDown:] ()
#130961 0x7fff96f9ad70 in forwardMethod ()
#130962 0x7fff96f9ad70 in forwardMethod ()
#130963 0x7fff96f9ad70 in forwardMethod ()
#130964 0x7fff96f9ad70 in forwardMethod ()
#130965 0x7fff96f9ad70 in forwardMethod ()
#130966 0x7fff96f9ad70 in forwardMethod ()
#130967 0x7fff974074ea in -[NSTabView mouseDown:] ()
#130968 0x7fff96f9ad70 in forwardMethod ()
#130969 0x7fff96f9ad70 in forwardMethod ()
#130970 0x7fff96f9ad70 in forwardMethod ()
#130971 0x7fff96f9ad70 in forwardMethod ()
#130972 0x7fff96f9ad70 in forwardMethod ()
#130973 0x7fff96f9ad70 in forwardMethod ()
#130974 0x7fff974074ea in -[NSTabView mouseDown:] ()
#130975 0x7fff96f9ad70 in forwardMethod ()
#130976 0x7fff96f9ad70 in forwardMethod ()
#130977 0x7fff96f9ad70 in forwardMethod ()
#130978 0x7fff96f9ad70 in forwardMethod ()
#130979 0x7fff96f9ad70 in forwardMethod ()
#130980 0x7fff97078718 in -[NSTitledFrame mouseDown:] ()
#130981 0x7fff9707857a in -[NSThemeFrame mouseDown:] ()
#130982 0x7fff96f9ad70 in forwardMethod ()
#130983 0x7fff96f9ad70 in forwardMethod ()
#130984 0x7fff9772e567 in -[NSTitlebarView mouseDown:] ()
#130985 0x7fff96f9ad70 in forwardMethod ()
#130986 0x7fff9707851c in -[NSToolbarView mouseDown:] ()
#130987 0x7fff96f9ad70 in forwardMethod ()
#130988 0x7fff96f9ad70 in forwardMethod ()
#130989 0x7fff970777fc in -[NSToolbarItemViewer mouseDown:] ()
#130990 0x7fff96f9ad70 in forwardMethod ()
#130991 0x7fff9751058f in -[NSWindow _reallySendEvent:] ()
#130992 0x7fff96f9c1bc in -[NSWindow sendEvent:] ()
#130993 0x00010014ae90 in -[SSYHintableWindow sendEvent:] at
/Users/jk/Documents/Programming/ClassesObjC/SSYHintableWindow.m:9
#130994 0x7fff96f4dd66 in -[NSApplication sendEvent:] ()
#130995 0x7fff96ddada8 in -[NSApplication run] ()
#130996 0x7fff96dc61b4 in NSApplicationMain ()
#130997 0x00011f5f in main at
/Users/jk/Documents/Programming/Projects/MyProj/main.m:83
#130998 0x00011de4 in start ()
The only stack entry in *my* code is at #130993, but it looks like my code
executes OK; the problem occurs when it invokes super.
@implementation SSYHintableWindow
- (void)sendEvent:(NSEvent *)event {
[SSYHintArrow removeIfEvent:event] ;
[super sendEvent:event] ;
}
@end
___
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: -[NSTabView mouseDown:] blows stack in Yosemite SDK
On Sep 28, 2014, at 9:48 PM, Jerry Krinock je...@ieee.org wrote: … #1309580x7fff96f9ad70 in forwardMethod () #1309590x7fff96f9ad70 in forwardMethod () #1309600x7fff974074ea in -[NSTabView mouseDown:] () Do you have a cycle in your nextResponder chain? Remember than NSViewController now inserts itself into the responder chain on 10.10. --Kyle Sluder ___ 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
Automatic data migration across two revisions
The last time I change my Core Data schema, I had to write a custom mapping model and classes. The automatic migration was able to find this class and use it to migrate the data. Now I've made a new change, and it's unable to migrate data from the old version to this latest version. Does the migration proceed in stages? That is, does it migrate version 5 - 7 by first migrating 5 - 6 and then 6 - 7? Or do I have to add yet another mapping model and classes to go from 5-7? The change from 6-7 seems to be handled automatically without problems. -- Rick Mann rm...@latencyzero.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
