> On 1 Oct 2015, at 5:04 pm, Peter Hudson wrote:
>
> Legacy code I’m afraid Graham - written some years ago.
> I simply want it to look better for now while we're getting on with the
> re-write.
> The new version indeed uses view-based table views - and works a lot better.
OK, so you’re impl
Legacy code I’m afraid Graham - written some years ago.
I simply want it to look better for now while we're getting on with the
re-write.
The new version indeed uses view-based table views - and works a lot better.
Peter
> On 1 Oct 2015, at 01:11, Graham Cox wrote:
>
>
>> On 30 Sep 2015,
> On 30 Sep 2015, at 10:20 pm, Peter Hudson wrote:
>
> As the user scrolls one of the table views, the system does not render all
> the details in the rows correctly.
> The most obvious one :- I draw my own lines between rows - inserting
> separator lines where appropriate.
> Hence, I overri
Sounds like you should be doing that in custom row views that draw the lines
when necessary
Sent from my iPhone
> On Sep 30, 2015, at 9:20 PM, Peter Hudson wrote:
>
> Many thanks for these ideas.
>
> As the user scrolls one of the table views, the system does not render all
> the details in
Many thanks for these ideas.
As the user scrolls one of the table views, the system does not render all the
details in the rows correctly.
The most obvious one :- I draw my own lines between rows - inserting
separator lines where appropriate.
Hence, I override drawRect. The process in here to
Check the NSScrollView notifications.
However you could try to observe changes to the NSClipView bounds.
You could also observe scroll events and so forth.
But ultimately you will run into semantics. Resting touches, momentum phases,
some slight ambiguity on whether the user feels done scrolling
