Hi,
My app registers some services and they work just fine. Only if I invoke then
from within the same application, the app hangs. I tried with other apps and
they had the same problem.
I searched the web for it but could not find anything.
Is there anything I can do about it?
Thanks
You didn't indicate what version of Mac OS X you were running under.
If this is happening under Snow Leopard, then this is a known issue in
Snow Leopard that Apple fixed in Lion.
The only work around I know is to put the service code in a separate
(background) application that then calls back
Hi Everyone,
My app has an NSCollectionView of devices, each with a custom icon.
I have a need to display the number of downloads happening from a given device.
The way that I want to do this, is to place a badge on each icon.
I have just tried to implement a clone of the NSDockTile badge that
On Jan 14, 2012, at 2:35 PM, Jerry Krinock wrote:
I want my app to access the new value of an object's property stored in an
sqlite store, after this value has been modified on disk by another process.
A few weeks ago, I did this, and I thought it was working:
[[obj
I tried replacing my Core Audio code for reading and decoding the music files
with calls to the AV Foundation framework. I was hoping that the defunct
assets.music.read-only entitlement would begin working if I used AV Foundation
instead. No joy. AVAsset cannot read the file (NO ==
Hi Jerry,
On 16 Jan 12 Jerry Krinock je...@ieee.org wrote:
It seems like gimme the latest value of object.foo from the disk shouldn't
be so hard.
It is indeed that hard, possibly for a good reason, but let's not go into that.
You've correctly handled the staleness interval. You may also
I'm not sure if this has already been suggested:
What if you don't update the UI unless the change is at least 1 sec or
1% or certain amount of bytes (whatever suits your needs better)?
Leo
On 1/15/12 12:33:31 AM, Andrew wrote:
Thank you all for the opinions. I left the code as-is in terms
Hi all, when I declare a property, something like:
@property(readwrite, copy, nonatomic) NSString *foo;
I will synthesize it with:
@synthesize foo;
But then I want to do some special processing when the value is set, so I
implement my setter:
- (void)setFoo:(NSString *)aFoo {
[self
Read the section Automatic Change Notification again and understand it has
nothing to do with properties or dot notation but just the method name.
Then look up automaticallyNotifiesObserversForKey and turn it off if you want
to code one key fully manually.
On 16 Jan, 2012, at 14:30, Gideon
On Mon, Jan 16, 2012 at 12:30 AM, Gideon King gid...@novamind.com wrote:
Are there any recommendations on the best approach for being able to have the
setter able to do what it needs with the KVO and then calling other methods,
without breaking bindings?
I can't believe I have misunderstood
Try overriding +[NSObject(NSKeyValueObserving)
automaticallyNotifiesObserversForKey:] to return NO for the properties you want
to handle manually.
On 2012-01-16, at 01:30, Gideon King wrote:
Hi all, when I declare a property, something like:
@property(readwrite, copy, nonatomic) NSString
Cool, thanks everybody. Nice that there is such a simple solution.
Regards
Gideon
On 16/01/2012, at 4:41 PM, Gordon Henriksen wrote:
Try overriding +[NSObject(NSKeyValueObserving)
automaticallyNotifiesObserversForKey:] to return NO for the properties you
want to handle manually.
On Jan 15, 2012, at 10:41 PM, Gordon Henriksen wrote:
Try overriding +[NSObject(NSKeyValueObserving)
automaticallyNotifiesObserversForKey:] to return NO for the properties you
want to handle manually.
Or just don’t call will/DidChange in your setter methods. You don’t need them
there —
You missed this in the original mail.
But the big thing for me is that I have a number of places throughout my
application where I need to have the changes made, the didChange notification
acted on by the observers, and then some other code run.
Which is why he wants to manually emit KVO
14 matches
Mail list logo
