On May 1, 2012, at 06:40 , Thibault Martin-Lagardette wrote: > The problem in the end is that not only do I have a visual glitch, but this > also feels like a very hacky/dirty solution, and hence, not the way to go. > I feel like I probably should not be trying to hide columns while some others > are resized. It works most of the time though, so this is very confusing.
What happens if you *don't* hide columns at all, but change your resizing code to set the width to 0 when a "hideable" column reaches its nominal min width? (Of course, you'd have to set the actual minWidth to 0 first.) If it turns out you must hide columns for other reasons (for example, the "hideable" columns are editable), then you could arrange to actually hide them at the end of the resizing process -- and you'd have to show them at the start, I suppose. Alternatively, assuming the table doesn't use a horizontal scroller, how about pushing "collapsed" columns (columns that have gone below their min width) out of the table view's bounds by resizing the non-collapsed columns? I'm not sure, but I think this might work given the position and order in which your columns should disappear. _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
