On Sun, Mar 17, 2013 at 1:50 AM, Kyle Sluder wrote:
> On Sat, Mar 16, 2013, at 06:37 PM, iain wrote:
> >
> >
> > On 17 Mar 2013, at 12:38 AM, Chuck Soper
> > > Each subview has an "NSLayoutConstraint * widthConstraint;" ivar that
> > > holds the absolute width. Visually, it looks like this:
> >
To pin the height of the documentView to its NSScrollView, I use the
following constraint:
NSDictionary * scrollViewsDict =
NSDictionaryOfVariableBindings(documentView);
[scrollView addConstraints: [NSLayoutConstraint
constraintsWithVisualFormat:
@"V:|[d
On Mar 17, 2013, at 9:37 AM, Kyle Sluder wrote:
>
> So that we're all on the same page: your internal vertical constraints can be
> expressed as @"V:|[subview1(>=70)][subview2(>=70)]…|". Then you add a
> constraint of @"|[documentView]|" to your scroll view.
Follow-up: if your goal here is to
Hello list,
just submitted this bug report to radar after banging for several hours one
this bug.
Maybe someone will find this an useful info, or even chime in with some quick
fix.
Summary: When a restorable window containing an autosaving NSSplitter is
restored on app launch, the tab order wi
In nibs we bind to NSUserDefaults through NSUserDefaultsController, but is
there any point in using NSUserDefaultsController when binding to a default
through code? (Or using KVO, also.) It's always seemed to work monitoring
NSUserDefaults directly.
--
Seth Willits
___
On Mar 17, 2013, at 1:06 PM, Seth Willits wrote:
> In nibs we bind to NSUserDefaults through NSUserDefaultsController, but is
> there any point in using NSUserDefaultsController when binding to a default
> through code? (Or using KVO, also.) It's always seemed to work monitoring
> NSUserDefault
On Mar 17, 2013, at 11:31 AM, Ken Thomases wrote:
>> In nibs we bind to NSUserDefaults through NSUserDefaultsController, but is
>> there any point in using NSUserDefaultsController when binding to a default
>> through code? (Or using KVO, also.) It's always seemed to work monitoring
>> NSUserDe
On Mar 17, 2013, at 6:00 PM, Seth Willits wrote:
> On Mar 17, 2013, at 11:31 AM, Ken Thomases wrote:
>
>>> In nibs we bind to NSUserDefaults through NSUserDefaultsController, but is
>>> there any point in using NSUserDefaultsController when binding to a default
>>> through code? (Or using KVO,
On 2013 Mar 16, at 07:46, Keary Suska wrote:
> You best bet is likely to turn to Core Foundation, which has built-in support
> for not only multi-user but also multi-computer…
That is correct, and also you'll need to do this in a privileged helper tool.
If you are fortunate enough to be requ
