On 11/21/12 7:56 AM, Kyle Sluder wrote:
On Wed, Nov 21, 2012, at 07:25 AM, Ross Carter wrote:
The way to do this is by subclassing NSGlyphGenerator to return null
glyphs for text that has your custom Hidden attribute. A WWDC video from
a few years back shows how.
Specifically, start watching
Seemingly simple problem. View in a panel window has a push-on/push-off
button. View has link to button (so I don¹t have to find it by tag). View
observes button state. Observer sets a color property according to button
state and calls [self setNeedsDisplay:YES]. Draw method fills view with
Sounds like NSButton is not KVO-compliant for `state`.
--Kyle Sluder
On Dec 1, 2012, at 7:55 AM, Gordon Apple g...@ed4u.com wrote:
Seemingly simple problem. View in a panel window has a push-on/push-off
button. View has link to button (so I don¹t have to find it by tag). View
observes
On 30 Nov 2012, at 23:05, Dave Fernandes dave.fernan...@utoronto.ca wrote:
On 2012-11-30, at 4:46 PM, Mike Abdullah cocoa...@mikeabdullah.net wrote:
On 30 Nov 2012, at 18:59, Dave Fernandes dave.fernan...@utoronto.ca wrote:
On 2012-11-30, at 6:42 AM, Mike Abdullah
I've been trying to hunt down a problem where Core Data will occasionally
refuse to save with the error
Dangling reference to an invalid object. I wrote up the details here:
http://www.mikeabdullah.net/dangling-ref-to-an-invalid-object.html
Can anyone shed some light on how this might happen?
Well, its bindings certainly work, and the observers works when its state is
changed by the distant (also bound) button.
On 12/1/12 10:29 AM, Kyle Sluder k...@ksluder.com wrote:
Sounds like NSButton is not KVO-compliant for `state`.
--Kyle Sluder
On Dec 1, 2012, at 12:48 PM, Gordon Apple wrote:
On 12/1/12 10:29 AM, Kyle Sluder k...@ksluder.com wrote:
Sounds like NSButton is not KVO-compliant for `state`.
Well, its bindings certainly work, and the observers works when its state is
changed by the distant (also bound) button.
On 2012-12-01, at 11:42 AM, Mike Abdullah cocoa...@mikeabdullah.net wrote:
One way to look at it is that NSPersistentDocument pretty much painted
itself into a corner from day 1, and it's too messy for Apple to untangle
that.
Can you elaborate?
Well it makes the assumptions that your
NSPersistentDocument always creates a MOC of type NSMainQueueConcurrencyType,
even if it is created on a background thread. So as long as things don't go
wrong during document opening, everything will be the same as a document
opened on the main thread forever after.
Whoops! I meant to say
Apparently, you are right. You¹re not going to believe the solution I came
up with. I added another button to the view with the same binding, linked
the view to it instead of the original one, then hid the new button. Now,
everything works correctly. If you can¹t skin a cat one way...
On
On Dec 1, 2012, at 1:09 PM, Gordon Apple g...@ed4u.com wrote:
Apparently, you are right. You’re not going to believe the solution I came
up with. I added another button to the view with the same binding, linked
the view to it instead of the original one, then hid the new button. Now,
Well, its a rather complex control panel using 100% bindings through a
number of generic object controllers and some fairly long binding paths.
Plus, I have never figured out how to pass ³self² with a bound action,
except that in one case I put in a link to from my window controller to a
button
I am trying to run the following one line echo bash script using NSUserUnixTask:
echo hello /dev/stderr
The Script file is named TaskLauncher and I have dropped it into my apps code
signed id folder in NSApplicationScriptsDirectory.
The task fails to launch and
On 1 Dec 2012, at 4:13 PM, jonat...@mugginsoft.com jonat...@mugginsoft.com
wrote:
NSURL *scriptsFolderURL = [[NSFileManager defaultManager]
...
error:error];
if (*error) {
On 1 Dec 2012, at 20:21, Dave Fernandes wrote:
NSPersistentDocument always creates a MOC of type
NSMainQueueConcurrencyType, even if it is created on a background thread. So
as long as things don't go wrong during document opening, everything will be
the same as a document opened on the
On 1 Dec 2012, at 20:12, Dave Fernandes wrote:
On 2012-12-01, at 11:42 AM, Mike Abdullah cocoa...@mikeabdullah.net wrote:
One way to look at it is that NSPersistentDocument pretty much painted
itself into a corner from day 1, and it's too messy for Apple to
untangle that.
Can you
On 2012-12-01, at 5:12 PM, Mike Abdullah cocoa...@mikeabdullah.net wrote:
- is comprised of a single Core Data store
- has a single managed object context
This definitely limits your options. But, is it necessary to support file
wrappers and iCloud? (Just trying to educate myself about
On 2012-12-01, at 5:05 PM, Mike Abdullah cocoa...@mikeabdullah.net wrote:
On 1 Dec 2012, at 20:21, Dave Fernandes wrote:
NSPersistentDocument always creates a MOC of type
NSMainQueueConcurrencyType, even if it is created on a background thread.
So as long as things don't go wrong during
18 matches
Mail list logo
