I’m using a
CPSplitViewwith master/detail divisions, a
CPScrollViewfor the detail and swapping in views loaded from other
cibs. And having no end of trouble getting the swapped-in views sized correctly. Does anyone have advice or experience to offer?
i am also seeing issues with autosave in CPSplitView since version 1.0
I’ll be trying XcodeCapp on a project or two tomorrow. There are indications already that tightened permissions in Big Sur might be a problem for project stored on another container. It is probably time to use the hardened runtime for XcodeCapp and to notarized it for binary distribution.
Both Big Sur and Xcode 12 have made significant progress (if early indications hold true) in dealing with the reliability and performance problems they’ve been bedevilled with for the last two release years.
Big Sur needs some serious visual tweaking but it seems remarkably and unusually stable, so far, for an Apple beta
@robert-plasq Installation from source needs to be tested, which requires installing a JVM and autoconf, automake and libtool (I use MacPorts, which must be compiled from source and is a nuissance. Don’t know where homebrew is at wrt Big Sur) - are you up for that?
I guess we'll see what happens. :)
@timhowell01 The problem with random failure reports converting
xibs within XcodeCapp hasn’t magically disappeared. The answer is, as now, to simply resave again. Have added this to my XcodeCapp cleanup list - a housecleaning is overdue.
One of the WWDC sessions concerned reading and writing files - will start by watching that to see why they considered that appropriate for a session.
@daboe01 @mrcarlberg I’ve continuing to work at my master/detail view (still using
CPSplitVew) and am making progress but still seeing strange things with swapped in
CPScrollViews. Scrollers are neither showing properly nor functioning for a swapped-in
I have settled on replacing the second of the two splitview’s subviews (the detail view) entirely with the detail view loaded from a
cib. The swapped-in subview will always have a
CPScrollView at its root. This allows visually confirming the detail view’s struts and springs are correctly set by resizing the view in IB. Previously, it was the second subview of the
CPSplitView which contained the (permanent, created at design time)
CPScrollView and its
contentView was the swapping target. This made it impossible to visually confirm the subview’s resize masks were set correctly.
With the permanent
CPScollView as the
CPSplitView’s second subview, scrollers worked properly, but it was a chore ensuring the swapped-in subviews had their resizing masks set correctly. Almost all content in the detail view needs a scroller at its root.
Curiously, the swapped-in
CPScrollView’s scroller frames are clearly present, but the scroll thumbs themselves are neither visible nor function (using scroll-wheel mouse). It’s not clear if the fault is in Cappuccino or my view configuration - but the scrollview’s visibility settings are IB’s defaults, which make them visible.
An approach which works but doesn’t answer the original problem. Use a permanent
CPScrollView as the second (detail) subview in the
CPSplitView. Use a root
CPScrollView in the detail view’s
cib for visual checking of resizing. When loading check to see if the
cib’s root view is a scroll view. If so, get its content view for swapping in, else get its root root view for swapping in. Document exhaustively so others won’t wonder wtf in the future.
Suggestions/comments about the original problem still welcome though.
CPTextView, even though all the others are working. Whether this is the fault of my own code or a problem with Cappuccino I need to understand what is happening.
@mrcarlberg A test case for swapping in a
CPScrollView to the second view in a
The standard procedure is probably to use a
CPView as a permanent detail view in the split and swap its subviews. I believe I’ve tried that and the swapped in scrollers are not working, as is the case here. Nevertheless, should the scrollers not work in this case? They don’t.