Matthew Reilly

@vadymmarkov Is there a list publicly available? I'd love to help out. Great library. :shipit:

If you are using new themes/toolbars, the positioning requires tweaking. ``` appMsg.setLayoutParams(getParams()); /** * The new theme requires some layout tweaking for croutons */ public FrameLayout.LayoutParams getParams() { FrameLayout.LayoutParams layoutParams...

@khirr I would really recommend using [Snackbar](http://developer.android.com/reference/android/support/design/widget/Snackbar.html)

Use setLayoutParams :)

``` appMsg.setLayoutParams(getParams()); /** * The new theme requires some layout tweaking for croutons */ public FrameLayout.LayoutParams getParams() { FrameLayout.LayoutParams layoutParams = new FrameLayout.LayoutParams( LinearLayout.LayoutParams.MATCH_PARENT, LinearLayout.LayoutParams.WRAP_CONTENT); layoutParams.setMargins(0, getSupportActionBar().getHeight(), 0, 0); return...

Seeing this as well. I think the issue is in the `targetContentOffset` function.

Yup, this only happens when `withScrollingVelocity` is non-nil.

@iwasrobbed I've been playing around with this and found something that may help. Manually calling: `collectionView.setContentOffset(targetContentOffset, animated: true)` at the end of the `targetContentOffset` if the `velocity` > 0 seems...

Yeah, it's not perfect. I think the solution may lie the CV itself. Per: http://stackoverflow.com/questions/15800111/uiscrollview-revert-to-starting-position-without-snaps

You should be able to utilize standard XML schemas - all IntelliJ-based editors will utilize those constraints.