Databases
StackOverflow2013
Postsdbo
PONSScrollView scrolling vertical scrolls horizontal
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONSScrollView scrolling vertical scrolls horizontal
    primarykey
    data
    text
    <p>If I scroll in my <code>NSScrollView</code> vertically it automatically scrolls horizontally. Why? I am using AGCenteringClipView as contentView.</p> <hr> <p>As you asked, here is the code of <strong>AGCenteringClipView.m</strong></p> <pre><code>#import "AGCenteringClipView.h" @implementation AGCenteringClipView - (id)initWithFrame:(NSRect)frameRect { self = [super initWithFrame:frameRect]; if (self) { mLookingAt = NSMakePoint(0, 0); [self setAutoresizesSubviews:NO]; } return self; } - (void)centerDocument { NSRect docRect = [[self documentView] frame]; NSRect clipRect = [self bounds]; // The origin point should have integral values or drawing anomalies will occur. // We'll leave it to the constrainScrollPoint: method to do it for us. if (docRect.size.width &lt; clipRect.size.width) { clipRect.origin.x = (docRect.size.width - clipRect.size.width) / 2.0; } else { clipRect.origin.x = mLookingAt.x * docRect.size.width - (clipRect.size.width / 2.0); } if (docRect.size.height &lt; clipRect.size.height) { clipRect.origin.y = (docRect.size.height - clipRect.size.height) / 2.0; } else { clipRect.origin.y = mLookingAt.y * docRect.size.height - (clipRect.size.height / 2.0); } // Probably the best way to move the bounds origin. // Make sure that the scrollToPoint contains integer values // or the NSView will smear the drawing under certain circumstances. [self scrollToPoint:[self constrainScrollPoint:clipRect.origin]]; // [[self superview] reflectScrolledClipView:self]; } // ---------------------------------------- // We need to override this so that the superclass doesn't override our new origin point. - (NSPoint)constrainScrollPoint:(NSPoint)proposedNewOrigin { NSRect docRect = [[self documentView] frame]; NSRect clipRect = [self bounds]; CGFloat maxX = docRect.size.width - clipRect.size.width; CGFloat maxY = docRect.size.height - clipRect.size.height; clipRect.origin = proposedNewOrigin; // shift origin to proposed location // If the clip view is wider than the doc, we can't scroll horizontally if (docRect.size.width &lt; clipRect.size.width) { clipRect.origin.x = round( maxX / 2.0 ); } else { clipRect.origin.x = round( MAX(0,MIN(clipRect.origin.x,maxX)) ); } // If the clip view is taller than the doc, we can't scroll vertically if (docRect.size.height &lt; clipRect.size.height) { clipRect.origin.y = round( maxY / 2.0 ); } else { clipRect.origin.y = round( MAX(0,MIN(clipRect.origin.y,maxY)) ); } // Save center of view as proportions so we can later tell where the user was focused. mLookingAt.x = NSMidX(clipRect) / docRect.size.width; mLookingAt.y = NSMidY(clipRect) / docRect.size.height; // The docRect isn't necessarily at (0, 0) so when it isn't, this correctly creates the correct scroll point return NSMakePoint(docRect.origin.x + clipRect.origin.x, docRect.origin.y + clipRect.origin.y); } // ---------------------------------------- // These two methods get called whenever the NSClipView's subview changes. // We save the old center of interest, call the superclass to let it do its work, // then move the scroll point to try and put the old center of interest // back in the center of the view if possible. - (void)viewBoundsChanged:(NSNotification *)notification { NSPoint savedPoint = mLookingAt; [super viewBoundsChanged:notification]; mLookingAt = savedPoint; [self centerDocument]; } - (void)viewFrameChanged:(NSNotification *)notification { NSPoint savedPoint = mLookingAt; [super viewFrameChanged:notification]; mLookingAt = savedPoint; [self centerDocument]; } // ---------------------------------------- // We have some redundancy in the fact that setFrame: appears to call/send setFrameOrigin: // and setFrameSize: to do its work, but we need to override these individual methods in case // either one gets called independently. Because none of them explicitly cause a screen update, // it's ok to do a little extra work behind the scenes because it wastes very little time. // It's probably the result of a single UI action anyway so it's not like it's slowing // down a huge iteration by being called thousands of times. - (void)setFrameOrigin:(NSPoint)newOrigin { if (!NSEqualPoints(self.frame.origin, newOrigin)) { [super setFrameOrigin:newOrigin]; [self centerDocument]; } } - (void)setFrameSize:(NSSize)newSize { if (!NSEqualSizes(self.frame.size, newSize)) { [super setFrameSize:newSize]; [self centerDocument]; } } - (void)setFrameRotation:(CGFloat)angle { [super setFrameRotation:angle]; [self centerDocument]; } </code></pre> <p>And NSScrollView has no code. It even is not subclassed.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. UShockeyman
    1. UShockeyman
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COCode please. "Why is X not working" is not a valid question today, seeing as my ESP tech got taken by the FBI.
      singulars
      1. PONSScrollView scrolling vertical scrolls horizontal
      1. USCodaFi
    2. COQuestion updated
      singulars
      1. PONSScrollView scrolling vertical scrolls horizontal
      1. UShockeyman
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload