<issue_start><issue_comment>Title: Capture main view touch events when drawer is open
username_0: In this PR I tried to solve this issue: https://github.com/root-two/react-native-drawer/issues/68

My idea is to let the main-view-container capture the touch-events when the drawer is open. In the original codes, drawer-container and main-view-container shared the same `onStartShouldSetPanResponder`, `onStartShouldSetPanResponderCapture`. This was not correct.

When the drawer is open, the drawer-container should not capture the touch-events, however, the main-view-container SHOULD capture the touch-events in order to block touches from child components on the main-view-container. Thus, the key changes I made in this PR is in `processShouldSet()`:
```
  if (inMask) {
      let toggled = this.processTapGestures()
      if (toggled) return viewType === VIEW_TYPE_DRAWER ? false : true  // The key change I made
      if (this.props.captureGestures && this.props.acceptPan) return true
    }
```

The original logics are quite complicated so I'm not sure whether my changes break anything, though my changes are simple. Would like to ask @username_1 to verify that! It works well on my drawer:
  ```
    <Drawer
        acceptPan
        captureGestures
        content={this._renderMenu()}
        negotiatePan={false}
        onClose={this.props.onClose}
        onOpen={this.props.onOpen}
        openDrawerOffset={0.1}
        panCloseMask={1}
        panOpenMask={0}
        panStartCompensation
        ref="drawer"
        styles={stylesRaw.drawer}
        tapToClose
        type="displace"
        tweenDuration={350}
        tweenHandler={this._handleTween}
        tweenEasing={'linear'}>
          {this.props.children}
      </Drawer>
```
<issue_comment>username_1: Ok I think I understand the need for this. but I think I might have a alternative solution. What if captureGestures only applied to the main when open and only apply to the drawer when closed. I think this would achieve the same functionality but be a little more generic. I cannot think of a use case where one would want to captureGestures in the other combinations.
<issue_comment>username_1: I will take this in and tinker with it a bit...
<issue_comment>username_1: @username_0 I took this in, but ended up heavily modifying it. I believe if you set `captureGestures='open'` it should only capture when the drawer is open. Also captureGestures is now much more aggresive in the capture logic and should work better now. Let me know how that goes! (`npm i react-native-drawer@next`)
<issue_comment>username_0: Hi @username_1 , thanks for updating! I tried `npm i react-native-drawer@next` but got an error like below. Do you know what happened?
![simulator screen shot mar 5 2016 10 02 42 pm](https://cloud.githubusercontent.com/assets/5363036/13552588/2958eeec-e31e-11e5-9667-78ef1aa2a23a.png)
<issue_comment>username_1: :tired_face: that should not have been a static class property. I fixed that, removed some console.log and improved the landscape orientation handling, and worked on captureGestures a bit more. new version out on @next tag.
<issue_comment>username_0: I tried the new version. When I click the button (on the main view) which is supposed to open the drawer, the drawer opens and then immediately closes. The drawer should open only.
<issue_comment>username_1: Odd, I tried your Drawer code from above and it is working in my application. There may be something weird going on within your onClose handler. A lot of things changed so it is hard to definitively say what change is causing this. 

Can you share your onClose/onOpen functions?
<issue_comment>username_0: Will do later today!
<issue_comment>username_0: Hi, I didn't define onClose / onOpen functions. The button I used to open my drawer calls `this.refs.menu.toggle()`, instead of `this.refs.menu.open()`. Is that the reason?
<issue_comment>username_0: Oh... I indeed defined onOpen handler, but I thought I won't have effects.

```
  _handleMenuOpen() {
    this.setState({ pressedMenuItem: null });
  }
```

I used pressedMenuItem to display which item I clicked on my drawer. If my removed this onOpen handler, it works good. But I don't understand why this matters..?
<issue_comment>username_1: hm, the setState will cause a re-render, which would indicate to me that there is some bug in the drawer related to re-renders. I will continue to dig deeper this week and report back if I figure out what is going on.
<issue_comment>username_0: Thanks :-)
<issue_comment>username_1: @username_0 I added you as a collaborator. No pressure, just thought that might make getting your PR's in a little easier :+1:
<issue_comment>username_0: got it!
<issue_comment>username_0: By the way, @username_1 , how does this fix go?
<issue_comment>username_1: haha sorry I forgot to update. I was able to recreate the problem, which iirc was caused by some bad logic in the declarative mode implementation. This I believe was the specific fix: https://github.com/root-two/react-native-drawer/commit/67431e7159eaddf0ae6ea3fedfb2805174861681#diff-168726dbe96b3ce427e7fedce31bb0bcR121
<issue_comment>username_0: Thanks for updates!
<issue_comment>username_1: overall I think v2 is very close. Waiting to get a little more feedback before flipping the switch on npm though.
<issue_comment>username_0: By the way, I'm not able to do `npm install react-native-drawer@next`, got `invalid`
<issue_comment>username_0: I pointed it to master and now it works
<issue_comment>username_2: Hi, I know this is is marked as closed but could anyone write an example of how to achieve the described behaviour? I cannot get it working.
Thanks in advance.
<issue_comment>username_1: 👍 there may not be an active release on the next tag anymore. Ill try to get a new major release out this week with Animated