On Dec 1, 2014, at 1:08 PM, Andreas Höschler wrote:
> Hi Kyle,
>
>>> Adding
>>>
>>> #ifdef __APPLE__
>>> - (void)setWindow:(NSWindow *)window
>>> {
>>> }
>>> #endif
>>>
>>> to my GSScrollView : NSScrollView subclass fixed (or at least worked
>>> around) the issue (no exception anymore and n
erface GSWindow : NSWindow
{
BOOL _suppressBecomingMainWin;
GSWindow *mainWin;
id filesOwner;
NSRect _tempRect;
}
Thanks,
Andreas
29/11/14 21:21:23,496 SOSmartBrowser[731]: Cannot remove an observer
for the key path "contentLayoutRect" from because it is not regist
On Dec 1, 2014, at 10:41 AM, Andreas Höschler wrote:
>
> Hi Jerry and all,
>
>>> You should look for … overrides of superclass properties
>>
>> Yes, indeed. Search for the AppKit Release Notes for OS X 10.10 Yosemite
>> and carefully read the section on tab views, wherein Apple has added alot
On Dec 1, 2014, at 10:41 , Andreas Höschler wrote:
>
> What the heck does that mean? How can they remove these access methods?
They didn’t. What they did is to change the access method declarations to
@property declarations. The change shows up in the API changes as a deletion
and and addition
Hi Jerry and all,
>> You should look for … overrides of superclass properties
>
> Yes, indeed. Search for the AppKit Release Notes for OS X 10.10 Yosemite and
> carefully read the section on tab views, wherein Apple has added alot of new
> stuff, which may be stepping on your old stuff.
Thank
> On Nov 30, 2014, at 12:24 AM, Jerry Krinock wrote:
>
> Search for the AppKit Release Notes for OS X 10.10 Yosemite and carefully
> read the section on tab views, wherein Apple has added alot of new stuff,
> which may be stepping on your old stuff.
Changing the subject, but isn't it odd tha
> On 2014 Nov 29, at 17:26, Ken Thomases wrote:
>
> You should look for … overrides of superclass properties
Yes, indeed. Search for the AppKit Release Notes for OS X 10.10 Yosemite and
carefully read the section on tab views, wherein Apple has added alot of new
stuff, which may be stepping
29/11/14 21:21:23,496 SOSmartBrowser[731]: Cannot remove an observer
> for the key path "contentLayoutRect" from 0x7d71cf50> because it is not registered as an observer.
> 29/11/14 21:21:23,499 SOSmartBrowser[731]: (
> 0 CoreFoundation 0x
Hi all,
we just tried one of our apps - doing fine on earlier versions of MacOSX - on
Yosemite. When clicking on a tab of a NSTabView we get the following on the
console and the app stops working (exception not caught):
29/11/14 21:21:23,496 SOSmartBrowser[731]: Cannot remove an observer
for
On Jun 26, 2009, at 3:43 AM, Tristan Celder wrote:
I've also filed a bug report 7010086 with example code attached. I
have no idea if it actually submitted however (I tried twice) as it
isn't appearing in 'my originated problems' and I am unable to
search for it... hopefully we'll get a fi
Hi Tristan,
On 26/6/09, Tristan Celder wrote:
I've also filed a bug report 7010086 with example code attached. I
have no idea if it actually submitted however (I tried twice) as it
isn't appearing in 'my originated problems' and I am unable to search
for it... hopefully we'll get a fix.
Thank
Hi Tristan,
On 26/6/09, Tristan Celder wrote:
The workaround I ended up using in the end was calling arrangeObjects
manually and turning off auto arrange content completely. Not ideal,
but it works...
I think that may only reduce the frequency of the exception. I
think I'm still getting the
I've also filed a bug report 7010086 with example code attached. I
have no idea if it actually submitted however (I tried twice) as it
isn't appearing in 'my originated problems' and I am unable to search
for it... hopefully we'll get a fix.
Cheers, Tristan.
On 26 Jun 2009, at 10:34, Trist
Hey Steve,
Thanks for your reply. Yeah, that's exactly it... the interface just
falls apart after the exception is raised. The workaround I ended up
using in the end was calling arrangeObjects manually and turning off
auto arrange content completely. Not ideal, but it works...
Cheers, Tri
Hi Tristan
On 25/6/09, cocoa-dev-requ...@lists.apple.com wrote:
Is there something I must do with CoreData to ensure KVO
compliance when using auto rearrange content? I have a small
project I've created to demonstrate this issue if anyone would
care to take a look...
I've moaned about thi
to access a relationship of the entity I am managing within an
array controller, yielding the following kind of error Cannot remove
an observer for the key path "person.name"
from , most likely because the value for the
key "person" has changed without an appropriate
t to Button's enable1 and selectedIndexes.count to
Button's enable2.
Now when I manipulate the collectionArray , add something or remove
something.
The Console will post "Cannot remove an observer for the key path "count" from
because it is not registered as an observer."
Now , I have
On Tue, May 6, 2008 at 2:27 PM, Steve Steinitz
<[EMAIL PROTECTED]> wrote:
> All my properties have a setters and getters and have the appropriate calls
> to
>
> will|did Access|Change ValueForKey
>
> before/after any change. Is there more that I need to do?
You don't say whether or not you
annot remove an observer for the key
path "name" from because it is not
registered as an observer.
"It" refers to the observer. -removeObserver:forKeyPath: raises this
exception if told to remove an object that isn't currently registered
as an observer. So what'
On May 4, 2008, at 10:07 PM, Jens Alfke wrote:
The usual cause of this is that you have a property that isn't KVO-
compliant. Something accesses your 'foo' property and registers as
an observer of that property, and also as an observer of the object
that's the property's current value; you c
On 4 May '08, at 3:35 PM, Steve Steinitz wrote:
Cannot remove an observer for the key path
"name" from because it is not registered as
an observer.
"It" refers to the observer. -removeObserver:forKeyPath: raises this
exception if told to remove an ob
Hello,
I now have two projects where I am getting the error below.
I've tried some obvious things like adding calls to will|did
Access|Change ValueForKey to my custom methods and also ensuring
key-value compliance by adding dummy setters. Here is the error.
Cannot remove an observer
on 4/28/08 12:49 PM, [EMAIL PROTECTED] purportedly said:
> Thanks. I think your hint worked. That is, I'm not sure what you were
> suggesting, but I took a guess, and it seems to have worked. But I
> still don't quite grasp what's going on, so I'm begging for a touch of
> background?
>
> What I
On Apr 25, 2008, at 7:42 PM, Keary Suska wrote:
on 4/25/08 6:49 PM, [EMAIL PROTECTED] purportedly said:
- (void) setEntry:(SVNWCEntry *)value
{
[self willChangeValueForKey:@"entry"];
[value retain];
[entry release];
entry = value;
[self didChangeValueForKey:@"entry"];
}
If you haven't tur
on 4/25/08 6:49 PM, [EMAIL PROTECTED] purportedly said:
> - (void) setEntry:(SVNWCEntry *)value
> {
> [self willChangeValueForKey:@"entry"];
>
> [value retain];
> [entry release];
> entry = value;
>
> [self didChangeValueForKey:@"entry"];
> }
If you haven't turned off automatic KVO notification
continue
very much longer (_not_ very much longer, actually), I'm likely to get
a BAD_ACCESS crash, which I suppose must be related.
2008-04-25 17:13:11.191 SCPluginUIDaemon[20884:10b]
Exception raised during posting of notification. Ignored.
exception: 'Cannot remove an
el for a Product.
Here is my problem. I noticed that changing the Model results
in two exception:
NSRangeException -- Cannot remove an observer
for the key path "currentCost"
from because it is not registered as an observer.
and
NSInternalInconsistencyException -- Canno
popup that allows the user
to change a Product's Model. The popup is usually only used to
fix data entry errors - e.g. specifying the wrong Model for a Product.
Here is my problem. I noticed that changing the Model results
in two exception:
NSRangeException -- Cannot remove an observe
28 matches
Mail list logo
