Vextil/WAMD — pull request #4 by David96 (2014-12-31 13:53:48+00:00)
Title: Fix sloppy animations by using FrameLayout instead of RelativeLayout

Somehow the RelativeLayout did to much onLayout calls to the FABMenu (I
don't know why). Using FrameLayout instead seems to fix that.
Furthermore, I changed the animation duration from the white shade from
500 to 300 to be the same as the FAB animation duration

The Java code of ConversationsLayout is now:
```Java
package ninja.vextil;

import android.content.Context;
import android.util.AttributeSet;
import android.view.MotionEvent;
import android.view.View;
import android.widget.FrameLayout;
import com.getbase.floatingactionbutton.FloatingActionsMenu;

public class ConversationsLayout extends FrameLayout {
View mOverlay;
FloatingActionsMenu mFABMenu;
public ConversationsLayout(Context context, AttributeSet attrs) {
super(context, attrs);
}

@Override
public void onFinishInflate() {
mOverlay = getChildAt(1);
mOverlay.setOnTouchListener(new OnTouchListener() {
@Override
public boolean onTouch(View v, MotionEvent event) {
mFABMenu.collapse();
return true;
}
});
mFABMenu = (FloatingActionsMenu)getChildAt(2);
mFABMenu.setOnFloatingActionsMenuUpdateListener(new FloatingActionsMenu.OnFloatingActionsMenuUpdateListener() {
@Override
public void onMenuExpanded() {
mOverlay.setVisibility(View.VISIBLE);
mOverlay.animate().alpha(1).setDuration(300);
}

@Override
public void onMenuCollapsed() {
mOverlay.animate().alpha(0).setDuration(300).withEndAction(new Runnable() {
@Override
public void run() {
mOverlay.setVisibility(View.GONE);
}
});
}
});
}
}
```