On Jan 29, 2010, at 9:03 PM, Jens Alfke wrote:
> I've been running into an intermittent bug involving NSOutlineViews with the 
> source-list highlight mode. In some cases the indentation of second-level 
> items is wrong: only a few pixels to the right instead of the specified 
> number (usually 16). You can see a screenshot here; note that the bottom two 
> items are too far to the left:
> http://chromium.googlecode.com/issues/attachment?aid=-3811668264974864615&name=Picture+75.png&inline=1
> 
> This only seems to happen only when there are just two levels of hierarchy 
> (top-level and sub-items), and if you add a third level, the view redraws 
> correctly and then stays correct even if the third level goes away later.
> 
> I've only seen this on 10.6.2, but I've now received a bug report for it that 
> comes from 10.5.8.
> 
> Is this a known issue? Is there a reliable workaround? (Setting the indent 
> level at awakeFromNib time does not help. I'm tempted to try adding and then 
> immediately removing a subfolder :-p )


I could be wrong of course but I suspect this has something to do with the 
outline view assuming the first level being "heading items". I dont know if 
there's a term for those items, basically what "Devices" is in Finder. The 
indentation in your screen shot exactly matches the indentation of the second 
level in Finder and my own source list.

I'm sure you have your reasons not to use those source list "heading" items but 
perhaps source list mode is not designed to handle this case.

Regards
Markus
--
__________________________________________
Markus Spoettl

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________

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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to