Re: [IB] Cells vs Controls in the Library
Re: [IB] Cells vs Controls in the Library
- Subject: Re: [IB] Cells vs Controls in the Library
- From: Christiaan Hofman <email@hidden>
- Date: Tue, 24 Aug 2010 17:10:19 +0200
On Aug 24, 2010, at 15:05, Stéphane Sudre wrote:
>
> On Aug 24, 2010, at 2:26 PM, Christiaan Hofman wrote:
>
>> [...]When you drag a control/cell, then it will be interpreted first as an control added as a subview to the NSTableView.
>
> No. It would just need to behave as it already does. A NSTableView does not accept a NSControl or NSView drop.
It does, because it's an NSView subclass (and therefore can have subviews), just try it if you don't believe me. It's the column that accepts the cell, but that would never be reached because it's being hidden by the enclosing tableview.
My other point is also that this is modular. when you somehow want to change the generic drop behaviuor you can only do that by adding all kinds of special conditions depending on the context like a tableview, and special conditions and exceptions are always the start of bugs.
Anyway my points are that you would gain much more than what you assume you do, and you would get all kinds of pitfalls and problems to work around, while complicating the API that's needed to support all that. That seriously sounds like a bad idea to me.
Christiaan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden