In the past, if I passed an object which was not encodeable, for example, an
NSManagedObject, or a collection containing such an object, to
-[NSKeyedArchiver archivedDataWithRootObject:], it would raise an exception and
print a warning to the console.
Now, if I pass it an unencodeable object,
Quincy:
Thanks for the answer! But something is still missing...
moveItemAtIndex:… does indeed move the items around to the proper places in the
tree, but the outline view control doesn’t update disclosure triangles.
Meaning, if I drag an item’s only child someplace else, the now-childless
Oh, hang on… I bet I need to wrap the moves in a begin/end updates block. I’ll
try that now.
—
Charles Jenkins
On Sunday, January 4, 2015 at 8:22 AM, Charles Jenkins wrote:
Quincy:
Thanks for the answer! But something is still missing...
moveItemAtIndex:… does indeed move the
No, begin/end updates didn’t help. I’m still having the problem described
below:
On Sunday, January 4, 2015 at 8:22 AM, Charles Jenkins wrote:
Quincy:
Thanks for the answer! But something is still missing...
moveItemAtIndex:… does indeed move the items around to the proper places
On Jan 4, 2015, at 7:22 AM, Charles Jenkins cejw...@gmail.com wrote:
moveItemAtIndex:… does indeed move the items around to the proper places in
the tree, but the outline view control doesn’t update disclosure triangles.
Meaning, if I drag an item’s only child someplace else, the
On 4 Jan 2015, at 21:22, Charles Jenkins cejw...@gmail.com wrote:
Quincy:
Thanks for the answer! But something is still missing...
moveItemAtIndex:… does indeed move the items around to the proper places in
the tree, but the outline view control doesn’t update disclosure triangles.
On 4 Jan 2015, at 21:33, Ken Thomases k...@codeweavers.com wrote:
On Jan 4, 2015, at 7:22 AM, Charles Jenkins cejw...@gmail.com wrote:
moveItemAtIndex:… does indeed move the items around to the proper places in
the tree, but the outline view control doesn’t update disclosure triangles.
On Jan 4, 2015, at 05:39 , Roland King r...@rols.org wrote:
I had to reload the parent row to get it to call the isItemExpandable and
other methods to either show a new disclosure triangle or remove one which
was no-longer valid.
That sounds at least halfway to being a bug. However, since
From: Jens Alfke j...@mooseyard.com
To: Eden Smallwood zeppenw...@lafn.org
I'm curious why you're doing this on 10.6. Is that the only OS version that
this behavior happens on?
—Jens
I’m endeavoring to keep my little shareware project back-compatible to
X.6
As
On Jan 4, 2015, at 2:43 PM, Eden Smallwood zeppenw...@lafn.org wrote:
Hey, readers, execute the following at the shell and post if ( result
!= 0 ) :
qlmanage -m | grep -v /System/Library | grep -v com.apple
I've got a bunch:
public.object-code - /Applications/Library
On 5 Jan 2015, at 02:13, Quincey Morris quinceymor...@rivergatesoftware.com
wrote:
On Jan 4, 2015, at 05:39 , Roland King r...@rols.org mailto:r...@rols.org
wrote:
I had to reload the parent row to get it to call the isItemExpandable and
other methods to either show a new disclosure
Thanks, all. I’ll reload parent items. In my app, whether an item has children
or not can change which icon appears in the tree, and the outline view has no
way to know about that without a reload to cause it to requery the delegate.
—
Charles Jenkins
On Sunday, January 4, 2015 at 7:06 PM,
12 matches
Mail list logo
