I don't know for sure, but you might be able to get around the 3rd party
plug-in issue by using runtime attributes instead.
--
Gary L. Wade (Sent from my iPad)
http://www.garywade.com/
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do
On Jul 19, 2012, at 11:06 , cocoa-dev-requ...@lists.apple.com wrote:
> Date: Thu, 19 Jul 2012 11:42:07 +0300
> From: Motti Shneor
> Message-ID:
>
> Thanks for the note. Indeed, RBSplitView is a complete, functional and
> feature-loaded class, but it is also lagging behind current Cocoa
> d
Hello Gideon.
Thanks for the note. Indeed, RBSplitView is a complete, functional and
feature-loaded class, but it is also lagging behind current Cocoa developments,
and does not integrate well XCode 4.x and with SDK 10.7 or and SDK 10.8.
Testing with it I saw problems in:
1. Look and feel (not
I always use RBSplitView - has all that stuff built in and more…
http://brockerhoff.net/blog/tag/rbsplitview/
Seems to work fine for my needs.
Regards
Gideon
On 03/07/2012, at 2:40 PM, Motti Shneor wrote:
> Thanks Graham (Sigh…)
>
> I was beginning to think I'm stupid or something, strug
Thanks Graham (Sigh…)
I was beginning to think I'm stupid or something, struggling so hard with a UI
element as ordinary as a Split-View.
I have the feeling I "almost got it", and I even think I understand why and
when delegate methods are being called. Rolling out my own SplitView doesn't
se
On Jul 3, 2012, at 12:11 , Andy Lee wrote:
> On Jul 3, 2012, at 10:31 AM, Rainer Brockerhoff wrote:
>> Now that's an interesting idea, thanks Andy! I'll look into it soon, I hope.
>
> P.P.S. I'm not sure how to deal with autolayout constraints that might get
> broken. Does replaceSubview:with: t
On Jul 3, 2012, at 10:31 AM, Rainer Brockerhoff wrote:
>
> On Jul 3, 2012, at 11:03 , Andy Lee wrote:
>
>> I haven't used RBSplitView, but it sounds like it might be handy to have a
>> method for replacing an already-set-up NSSplitView with an RBSplitView.
>> Maybe it could be a category meth
On Jul 3, 2012, at 10:31 AM, Rainer Brockerhoff wrote:
> On Jul 3, 2012, at 11:03 , Andy Lee wrote:
>
>> I haven't used RBSplitView, but it sounds like it might be handy to have a
>> method for replacing an already-set-up NSSplitView with an RBSplitView.
>> Maybe it could be a category method on
On Jul 3, 2012, at 11:03 , Andy Lee wrote:
> I haven't used RBSplitView, but it sounds like it might be handy to have a
> method for replacing an already-set-up NSSplitView with an RBSplitView. Maybe
> it could be a category method on NSSplitView, something like this:
> ...
> This way you can s
I haven't used RBSplitView, but it sounds like it might be handy to have a
method for replacing an already-set-up NSSplitView with an RBSplitView. Maybe
it could be a category method on NSSplitView, something like this:
- (RBSplitView *)replaceWithRBSplitView
{
// Retain and autorelease
On Jul 3, 2012, at 01:46 , cocoa-dev-requ...@lists.apple.com wrote:
> Date: Tue, 03 Jul 2012 10:14:21 +1000
> From: Graham Cox
> Message-ID:
>
> On 03/07/2012, at 12:21 AM, Motti Shneor wrote:
>
>> I really need an advice here.
>
> This will sound flippant but it's not meant to be: implement
Thanks again Graham and all the rest --- We're going somewhere now.
On 3 ביול 2012, at 08:22, Graham Cox wrote:
>
> On 03/07/2012, at 2:46 PM, Motti Shneor wrote:
>
>> have the feeling I "almost got it", and I even think I understand why and
>> when delegate methods are being called. Rollin
On Tue, Jul 3, 2012, at 03:22 PM, Graham Cox wrote:
> True in part. But you could subclass NSView instead. After all,
> NSSplitView doesn't really bring that much to the table - it relies on
> inheriting NSView to store its subviews, the only thing it draws is the
> actual splitter itself, which is
On 03/07/2012, at 2:46 PM, Motti Shneor wrote:
> have the feeling I "almost got it", and I even think I understand why and
> when delegate methods are being called. Rolling out my own SplitView doesn't
> seem to be easier than finding the answer to my question, because to inherit
> from NSSp
On Jul 2, 2012, at 21:46 , Motti Shneor wrote:
> for god sake, why isn't there a [mySplitView setSubview:panelSubview
> collapsedStateTo:YES/NO]
Well, one possible answer is to ask yourself if you're asking the right
questions.
I think there's perhaps a small difference between the user c
On Jul 2, 2012, at 9:46 PM, Motti Shneor wrote:
> Thanks Graham (Sigh…)
>
> I was beginning to think I'm stupid or something, struggling so hard with a
> UI element as ordinary as a Split-View.
I ran into this exact same problem last week. I can't believe it is an
extremely rare situation.
I
Thanks Graham (Sigh…)
I was beginning to think I'm stupid or something, struggling so hard with a UI
element as ordinary as a Split-View.
I have the feeling I "almost got it", and I even think I understand why and
when delegate methods are being called. Rolling out my own SplitView doesn't
se
On 03/07/2012, at 12:21 AM, Motti Shneor wrote:
> I really need an advice here.
This will sound flippant but it's not meant to be: implement your own split
view.
NSSplitView is the most bizarre piece of design and difficult to get to behave
just how you want even in simple cases like having
Hello everyone.
I have an NSSplitView with dynamic contents (views can be added and deleted in
runtime). Views can also be collapsed by the user, or programmatically at
certain situations.
My problem is this. Each of my views has a minimum size and a maximum size,
that must be met anytime, or
The TwoManyControllers sample code does what you want I think mostly
generated from declarative as far as I can see
On 4 Aug 2008, at 06:41, Graham Cox wrote:
This is not any thing to do with NSSplitView as such. You're asking
"how to implement a master-detail interface". Try doing searchin
Am Mo,04.08.2008 um 07:35 schrieb Eric Lee:
Sorry, I accidently did something wrong on that message. Here's the
one I'm actually asking...
How do you make a NSSplitView so that when you click something on
one side, the other side is updated. For example, take the mail
application. When
This is not any thing to do with NSSplitView as such. You're asking
"how to implement a master-detail interface". Try doing searching on
those terms, phrase or a variation of it, I'm sure it's been well-
covered.
The essentials are - detect the selection change in the master view,
use it t
Sorry, I accidently did something wrong on that message. Here's the
one I'm actually asking...
How do you make a NSSplitView so that when you click something on one
side, the other side is updated. For example, take the mail
application. When you click trash, the other side is updated to
I have two table views with two different data, and I have two buttons
so that when you press one button, something is added to the first
table view, and when you press the second button, some info is added
to the second table view. You can't press the 1st one to add it to the
2nd table vie
24 matches
Mail list logo