Re: Displaying a sheet immediately after a window is opened
On 17 Aug 2012, at 00:11, Rick Mann wrote: > I'm surprised this is so hard to do. I'd argue that rather than a pair of animations, what you better is to open the window non-animated, and then animate the sheet over it. Have you looked into that? ___ 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: Displaying a sheet immediately after a window is opened
It's the default behavior. -- Rick On Aug 17, 2012, at 2:03, Mike Abdullah wrote: > > On 17 Aug 2012, at 00:11, Rick Mann wrote: > >> I'm surprised this is so hard to do. > > I'd argue that rather than a pair of animations, what you better is to open > the window non-animated, and then animate the sheet over it. Have you looked > into that? > ___ 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: initial value of an NSPopupButton shows with delay
On Aug 16, 2012, at 8:50 PM, Peter Ammon wrote:
> Is your window set to be visible at launch (i.e. in IB)? Try making it not
> visible at launch, and then ordering it onscreen after the nib is loaded.
> That should allow all the awakeFromNib methods to run before the window
> appears.
Hi Peter,
Your answer made me realize that I am using some fading animation to swap the
views in and out:
if ( oldView )
{
fadeOut = [NSDictionary dictionaryWithObjectsAndKeys: oldView,
NSViewAnimationTargetKey, NSViewAnimationFadeOutEffect,
NSViewAnimationEffectKey, nil];
}
fadeIn = [NSDictionary dictionaryWithObjectsAndKeys: newView,
NSViewAnimationTargetKey, NSViewAnimationFadeInEffect,
NSViewAnimationEffectKey, nil];
NSAnimation *animation = [[NSViewAnimation alloc]
initWithViewAnimations:[NSArray arrayWithObjects: fadeOut, fadeIn, nil]];
animation.duration = 0.25;
[animation startAnimation];
Once I comment out the last line, the view is loaded immediately, and the popup
default title as well. When I set the animation time to a long time sec, I am
able to read what it says before "default" name, and it is something like
(entity: MyEntity; id 0x101441630
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Re: Displaying a sheet immediately after a window is opened
On 16/08/2012, at 1:02 PM, Rick Mann wrote: > After googling, I found that in -[NSDocument windowControllerDidLoadNib], I > had to begin my sheet by calling performSelector on the main thread (actually > I scheduled a block operation). This is kinda gross, but seems to work. > > Unfortunately, the result is that the main window animates opening > simultaneously with the sheet animating open. > > I'd really like the sheet to begin its animation after the main window > finishes its own. Is there a "right" place to do this? > Why not just put a few seconds' delay in the performSelector: call? --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: Displaying a sheet immediately after a window is opened
On Aug 17, 2012, at 3:38 , Graham Cox wrote: > > On 16/08/2012, at 1:02 PM, Rick Mann wrote: > >> After googling, I found that in -[NSDocument windowControllerDidLoadNib], I >> had to begin my sheet by calling performSelector on the main thread >> (actually I scheduled a block operation). This is kinda gross, but seems to >> work. >> >> Unfortunately, the result is that the main window animates opening >> simultaneously with the sheet animating open. >> >> I'd really like the sheet to begin its animation after the main window >> finishes its own. Is there a "right" place to do this? >> > > > Why not just put a few seconds' delay in the performSelector: call? Doesn't that seem like a hack to you? How many seconds? I find that to be a rather gross solution, and one I'm specifically trying to avoid. It was bad enough that I had to do it as a performSelector call -- Rick ___ 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: Displaying a sheet immediately after a window is opened
On 8/16/12 5:02 AM, Rick Mann wrote:
After googling, I found that in -[NSDocument windowControllerDidLoadNib], I
had to begin my sheet by calling performSelector on the main thread (actually
I scheduled a block operation). This is kinda gross, but seems to work.
Unfortunately, the result is that the main window animates opening
simultaneously with the sheet animating open.
I'd really like the sheet to begin its animation after the main window
finishes its own. Is there a "right" place to do this?
Don't know about right place, I'm doing this by overwriting -showWindow: in the
window controller, firing a delayed performSelector with 0.5 seconds delay. I
also tried -windowDidLoad but as you noticed, the animation isn't complete when
it being called. Long story short:
- (void)showWindow:(id)sender
{
[super showWindow:sender];
[self performSelector:@selector(showMySheet:)
withObject:nil
afterDelay:0.5];
}
Works well for me, both on Lion and Mountain Lion.
Regards
Markus
--
__
Markus Spoettl
___
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
NSBrowser fills NSPasteboard but won't drop
I have an NSBroswer with a series of entries that look up a text blob. If the blob exists then: - (BOOL)browser:canDragRowsWithIndexes:inColumn:withEvent: returns YES. This invokes - (BOOL)browser:writeRowsWithIndexes:inColumn:toPasteboard: In here I do the following: NSUInteger changeCount; BOOL retBOOL = YES; changeCount = [pasteboard clearContents]; changeCount = [pasteboard declareTypes:@[NSPasteboardTypeString, NSPasteboardTypeHTML] owner:self]; didSet = [pasteboard setString:self.currentHTMLCode forType:NSPasteboardTypeString]; retBOOL = retBOOL & didSet; didSet = [pasteboard setString:[NSString stringWithFormat:@"%@", self.currentHTMLCode] forType:NSPasteboardTypeHTML]; retBOOL = retBOOL & didSet; Now the data analysis of the pasteboard coming out (with retBOOL: Yes) is: pasteboard: : name: : Apple CFPasteboard drag change count: : 77 types: : ( "public.utf8-plain-text", NSStringPboardType, "public.html", "Apple HTML pasteboard type" ) items: : ( "" ) PBItem: : PBType: : public.utf8-plain-text String for type [public.utf8-plain-text] = 89958 characters PBType: : public.html String for type [public.html] = 89969 characters retValue: YES So my problem is that when I drag this to SimpleText or BBEdit, nothing drops. I don't see a highlight of the target document. (Note: I also have a drag image routine, and I see the drag image) Any ideas why I seem to be populating the pasteboard but it refuses to drop in the other app? Thanks, -Andrei ___ 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
invoke java through AuthorizationExecuteWithPrivileges() then jvm comes up without ipv6 ?
Hi, I am invoking java in 2 ways in 10.6.8 Option1 -- If i execute /usr/bin/java from Runtime().exec(), then jvm comes up with ipv6 support Option2 --- whereas if i invoke java through AuthorizationExecuteWithPrivileges() then jvm comes up without ipv6. precisely, in option1, i can see urlconnection is able to connect to ipv6 address whereas in option2, i got protocol family unavailable. I am using AuthorizationExecuteWithPrivileges() through authKit jar on 10.6.8 and JVM is 1.6. Any pointers. -Rajendran P ___ 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
Apple Aperture-like look & feel
Hi I am wondering what does it take to make panels/buttons that customized, like it is done in Apple Aperture? Did Apple developers paint every dialog element manually? Are there some classes already available that would allow to "theme up" an app like this? Thank you ___ 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: Apple Aperture-like look & feel
Since not all of us have Aperture, can you point us to a screenshot of what you are aiming for? On Aug 17, 2012, at 3:27 PM, Nick wrote: > Hi > > I am wondering what does it take to make panels/buttons that > customized, like it is done in Apple Aperture? Did Apple developers > paint every dialog element manually? Are there some classes already > available that would allow to "theme up" an app like this? > > Thank you > ___ > > 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/zav%40mac.com > > This email sent to z...@mac.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
Re: Apple Aperture-like look & feel
Aperture interface looks like this: http://www.cifoto.ru/wp-content/uploads/2012/05/12-05-14-raw-convertery-2.jpg 2012/8/17 Alex Zavatone : > Since not all of us have Aperture, can you point us to a screenshot of what > you are aiming for? > > On Aug 17, 2012, at 3:27 PM, Nick wrote: > >> Hi >> >> I am wondering what does it take to make panels/buttons that >> customized, like it is done in Apple Aperture? Did Apple developers >> paint every dialog element manually? Are there some classes already >> available that would allow to "theme up" an app like this? >> >> Thank you >> ___ >> >> 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/zav%40mac.com >> >> This email sent to z...@mac.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
Re: Apple Aperture-like look & feel
While I cannot say Aperture does this, when it comes to drawing a uniquely themed UI, you might find these draw functions in AppKit to be useful: https://developer.apple.com/library/mac/#documentation/Cocoa/Reference/Appl icationKit/Miscellaneous/AppKit_Functions/Reference/reference.html Look in particular at NSDrawThreePartImage and NSDrawNinePartImage. -- Gary L. Wade http://www.garywade.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
Re: Apple Aperture-like look & feel
To get many of these types of controls, I believe that in the Flash or web world world, this was referred to 9 slice scaling or 3 slice scaling. If you're going to have buttons that are are Macish, and you will source your own graphics, you don't want to focus on anything that's not compatible with 3 slice scaling if the button will have a variable width. This means that you have a graphic that consists of a button's caps, or left and right ends and a middle pixel column that can be stretched as wide as needed to be the middle fill for a button. For that scroll bar thumb, you're simply doing the same thing the other way. So, pardon me on this, but I only have experience drawing buttons in iOS in code and the storyboard, using Xcode 4.x so I'm not sure what the approach on Mac OS would be but... I do know that on iOS, when you specify a graphic for a button, it will be stretched out and will look bad in the storyboard, but the button drawing code will act as if the graphic supplied is 3 slice compatible and it will render out perfectly, without you having to write any code at all. That in itself is really nice. Unless there already is a formal process I don't know about to tint the GUI laid out in an XIB in code, you'll want to focus on graphics that meet the 3 slice scaling requirements and if you're going to product them yourself, doing them as vector graphics in Illustrator or Photoshop and then exported to Photoshop and trimmed using Image: Trim, then saved out as PNGs is the way to go. These can then be applied to the button for tis various graphic states, so make sure you have consistent graphic looks for each state that you want to use. I'm sure you can find many samples on the web to play with as an experiment, but I have a few sample PNG and AI files that show the 3 slice concept if you want them. The rest of this gets a little long, but it might be nice to read if you want to visualize how you could implement this yourself and just how many graphics you might need to do it. In the past, for the simplest button case, I've used these following states in button logic, each requiring its own 3 slice graphic and a hit map graphic to indicate when to change the button graphic. The hit map is a 2 bit image taken off of the Active graphic's button's shape boundary, but you won't need one of these for Mac OS. Active state - clickable, visible and not disabled and in the mouse up/finger up state. Over state - mouse or interaction area (finger blob) is over the hit map of the button. Triggered off intersection of the mouse/finger with the hit map graphic. Down state - finger or mouse is pressed down when the over state condition is satisfied. Disabled state - not clickable, visible and disabled. Selected state - when a button has an other property such as being part of a tab bar often you'll want to show graphically that "I'm enabled and selected". Other times, you want it to show that it's selected, but don't want it to be clickable. This can present challenges and if the button's never going to be disabled, you can simply repurpose that graphic for the disabled case. "I've been clicked, show I'm selected but not clickable". Or selected and clickable can be another state for an enabled button, it's up to you. When I had to build my own UI foundation classes a long long time ago, doing things like button groups and radio buttons involved the logic for the following four standard button states: - Active - Rollover - Down - Disabled in both the toggled on and toggled off state. To allow this toggled on/off feature, the logic for "am I toggled on or not" was simply another class that could be added to the inheritance chain to enable this functionality. This added a meta state called Toggled to the four button states seen above and naturally required graphics for those states as well, resulting in up to 8 button graphics - which is not always desirable. These 8 states are perfect for checkboxes since the all those 4 states will be able to exist in the toggled and untoggled state. The thing was that sometimes in radio button groups, you can have a group that is all disabled, but with one of the buttons in the toggled on state. Also, in radio button groups, you'll never want a radio button that appears with the Toggled, active, mouse up state to respond to clicks, mouseover or mouseDown. So this almost breaks the model and creates too much graphic overhead. What was introduced to handle this was simply to allow graphic files to be also be a 1 variable class that simply pointed to the identifier for the graphic file you really wanted to use in its place. For radio buttons, the Toggled On files for Rollover and Down states can simply point to the Active graphic and the user will only see the Toggled Active graphic if they try to interact with it. You'll only end up with the need for 6 state graphic files instead of 8 and there are
Re: Apple Aperture-like look & feel
Here are some of the other screenshots.. I wonder what would it take to create something like that.. They even customized the menus (it has black background and a custom fount).. http://itc.ua/files/pics/2(713).jpg http://sgalagan.com/wp-content/uploads/2012/06/aperture-search-window-add-rule.jpg 2012/8/17 Nick : > Hi > > I am wondering what does it take to make panels/buttons that > customized, like it is done in Apple Aperture? Did Apple developers > paint every dialog element manually? Are there some classes already > available that would allow to "theme up" an app like this? > > Thank you ___ 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: Apple Aperture-like look & feel
On Aug 17, 2012, at 4:31 PM, Nick wrote: > Here are some of the other screenshots.. I wonder what would it take > to create something like that.. > They even customized the menus (it has black background and a custom fount).. > > > http://itc.ua/files/pics/2(713).jpg I think that is Adobe Lightroom, not Aperture. Marc ___ 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: Apple Aperture-like look & feel
On Aug 17, 2012, at 7:36 PM, Marco S Hyman wrote: > On Aug 17, 2012, at 4:31 PM, Nick wrote: > >> Here are some of the other screenshots.. I wonder what would it take >> to create something like that.. >> They even customized the menus (it has black background and a custom fount).. >> >> >> http://itc.ua/files/pics/2(713).jpg > > I think that is Adobe Lightroom, not Aperture. Sure looks like it. In any case Nick, I'm one of the two guys who did the functional prototypes of FiOS TV for Verizon, so if you need some Illustrator graphics modeled off of those, I wouldn't mind helping you out if you need a few graphic items cooked up. The top bar that holds the drive icon in the Lightroom image is easy-ish to make. The Source panel on the left with the treeview would be a good exercise for me to code and create graphics for iOS, though I'm not sure how it would go together properly for MacOS. I do have deliverables over the weekend, but if you are planning on giving this a go, let me know. Cheers, - Alex ___ 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
CGXDisableUpdate?
It appears that my program hangs after the following console log events: 8/17/12 3:15:11.555 PM WindowServer[104]: CGXDisableUpdate: UI updates were forcibly disabled by application "X" for over 1.00 seconds. Server has re-enabled them. 8/17/12 3:15:25.556 PM WindowServer[104]: disable_update_likely_unbalanced: UI updates still disabled by application "X" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call. I am not directly calling CGXDisableUpdate anywhere in my code. Any ideas what causes this? Best regards, John MacMullin ___ 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: CGXDisableUpdate?
On Aug 17, 2012, at 5:44 PM, John MacMullin wrote: > It appears that my program hangs after the following console log events: > > 8/17/12 3:15:11.555 PM WindowServer[104]: CGXDisableUpdate: UI updates were > forcibly disabled by application "X" for over 1.00 seconds. Server > has re-enabled them. > 8/17/12 3:15:25.556 PM WindowServer[104]: disable_update_likely_unbalanced: > UI updates still disabled by application "X" after 15.00 seconds > (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced > disableUpdate call. > > I am not directly calling CGXDisableUpdate anywhere in my code. > > Any ideas what causes this? Are you processing images? I'll get it by dropping a large raw image into an image well on my oldish iMac. I see it when Aperture is processing images, too. Marc ___ 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
Calculating row heights for view-based table rows, on re-use throws error
Hello all,
I have a view-based table in which there are four distinct row types,
representing distinct object types which may appear. The tableRowViews are in
the nib and represented in the code here as xxxCellView entities.
- (CGFloat)tableView:(NSTableView *)tableView heightOfRow:(NSInteger)row {
id obj = [_content objectAtIndex:row];
if([obj isKindOfClass:[RSPostalAddress class]]) {
return self.postalCellView.bounds.size.height;
}
else if([obj isKindOfClass: [RSEmailAddress class]]) {
return self.emailCellView.bounds.size.height;
}
else if([obj isKindOfClass: [RSPhoneNumber class]]) {
return self.phoneCellView.bounds.size.height;
}
else { // note field
return self.notesCellView.bounds.size.height;
}
}
My problem is that on first pass, this code returns quite sane and reasonable
results: the manually set sizes of the prototype tableRowViews. However on
second pass, it goes insane: 132.0 becomes 266.0, 28.0 becomes 118.0, 104.0
becomes 210.0 ... And the next thing the -tableView:heightOfRow: does is throw
it's brain in the air and gives up …. :P
2012-08-17 18:51:52.766 RSSuperContactsX[24075:303] -[RSTableController
tableView:heightOfRow:]- [0136] self.postalCellView.bounds.size.height:
266.00
2012-08-17 18:51:52.766 RSSuperContactsX[24075:303] -[RSTableController
tableView:heightOfRow:]- [0136] self.postalCellView.bounds.size.height:
266.00
2012-08-17 18:51:52.766 RSSuperContactsX[24075:303] -[RSTableController
tableView:heightOfRow:]- [0140] self.emailCellView.bounds.size.height:
118.00
2012-08-17 18:51:52.766 RSSuperContactsX[24075:303] -[RSTableController
tableView:heightOfRow:]- [0140] self.emailCellView.bounds.size.height:
118.00
2012-08-17 18:51:52.767 RSSuperContactsX[24075:303] -[RSTableController
tableView:heightOfRow:]- [0144] self.phoneCellView.bounds.size.height:
118.00
2012-08-17 18:51:52.767 RSSuperContactsX[24075:303] -[RSTableController
tableView:heightOfRow:]- [0148] self.notesCellView.bounds.size.height:
210.00
2012-08-17 18:51:52.767 RSSuperContactsX[24075:303] *** -[__NSArrayM
objectAtIndex:]: index 6 beyond bounds [0 .. 5]
2012-08-17 18:51:52.769 RSSuperContactsX[24075:303] (
0 CoreFoundation 0x7fff900a8716
__exceptionPreprocess + 198
1 libobjc.A.dylib 0x7fff8ad98470
objc_exception_throw + 43
2 CoreFoundation 0x7fff900455dc -[__NSArrayM
objectAtIndex:] + 252
3 RSSuperContactsX0x000130f5
-[RSTableController tableView:heightOfRow:] + 101
4 AppKit 0x7fff8a2e3322
-[NSTableView _sendDelegateHeightOfRow:] + 130
5 AppKit 0x7fff8a2e30db
-[NSTableView _uncachedRectHeightOfRow:] + 197
6 AppKit 0x7fff8a2e2f7a
-[_NSTableRowHeightStorage _cacheRowHeights] + 241
7 AppKit 0x7fff8a29d6f5
-[_NSTableRowHeightStorage _ensureRowHeights] + 80
8 AppKit 0x7fff8a2e3469
-[_NSTableRowHeightStorage copyWithZone:] + 89
9 AppKit 0x7fff8a2e03eb
-[NSTableRowData _saveCurrentRowHeightState] + 293
10 AppKit 0x7fff8a2e0282
-[NSTableRowData beginUpdates] + 93
11 AppKit 0x7fff8a29be0b
-[NSTableView _beginUpdate] + 63
12 AppKit 0x7fff8a2b473d
-[NSTableView reloadData] + 33
13 RSSuperContactsX0x00013016
-[RSTableController setPerson:] + 2982
14 RSSuperContactsX0x0001240b
-[RSTableController setActivePerson:] + 779
My expectation is that I ought to be able to clear the table (iterating through
the rows and applying -removeRowsAtIndexes:withAnimation: to discard the
present rowViews, and start clean with the next record to be displayed,
generating new rowViews as needed (because the number of component elements
(phone numbers/email addresses/etc) will vary from one record to the next).
I have no iterator code running at the time this error occurs, so I suspect I
have failed to correctly setup some aspect of the tableView/rowView mechanics.
Does anything suggest itself to anyone ?
Hopefully,
Erik
___
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
