Re: curious: if not file references, what?

> On Jan 20, 2017, at 10:24 PM, Quincey Morris > wrote: > > It’s an interesting question whether file-references use inode numbers. Some > file systems don’t have them, so (I assume) they’re invented when such a file > system is mounted, but they’re not necessarily assigned permanently across

Re: curious: if not file references, what?

On Jan 20, 2017, at 19:10 , David Young wrote: > > This discussion seems to connect with a question I have had: what's the > "proper" way to refer from a first document to a second document, if > the second document may not have a fixed location in the filesystem? > It sounds like "file reference

curious: if not file references, what?

This discussion seems to connect with a question I have had: what's the "proper" way to refer from a first document to a second document, if the second document may not have a fixed location in the filesystem? It sounds like "file references" (perhaps these are roughly in correspondence with an ino

Re: Merging scrolling/clipping with NSStackView

> On 20 Jan 2017, at 21:36, Quincey Morris > wrote: > > On Jan 20, 2017, at 02:47 , Jonathan Mitchell > wrote: >> >> NSTableView might go something like this: >> >> @implementation TSTableView >> >> - (NSSize)intrinsicContentSize >> { >> NSSize size

Re: Merging scrolling/clipping with NSStackView

On Jan 20, 2017, at 02:47 , Jonathan Mitchell wrote: > > NSTableView might go something like this: > > @implementation TSTableView > > - (NSSize)intrinsicContentSize > { > NSSize size = [super intrinsicContentSize]; > NSInteger nr = [self numberOfRows]; > CGFloat

Re: Merging scrolling/clipping with NSStackView

> On 19 Jan 2017, at 18:25, Quincey Morris > wrote: > > On Jan 19, 2017, at 06:39 , Daryle Walker wrote: >> >> The inner views should be as tall as they need to be. > > I don’t understand this part. How tall is that? > > I assume you mean that you want the text and table views to be tall en