MTInnerWindow and grab

[Jonathan Gossage]

In the class MTInnerWindow the on_touch_down function grabs the touch
if it gets a True return from the dispatch of the touch to the inner
window controls. However, on_touch_up does not have a corresponding
ungrab call. Is this by design or is it an oversight?

[Thomas Hansen]

does it make a difference to put it there? once the touch is gone,
its gone, so what difference would it make? maybe i'm overlooking
something.

--
Thomas

> --
> You received this message because you are subscribed to the Google Groups "pymt-dev" group.
> To post to this group, send email to pymt...@googlegroups.com.
> To unsubscribe from this group, send email to pymt-dev+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/pymt-dev?hl=en.
>
>

[Jonathan Gossage]

Two reasons:

1. General practice with grabbing is that the object that grabs a touch should release the touch.

2. If MTInnerWindow is sub-classed by another widget, when the touch returns to the subclass of MTInnerWindow, it still shows as being grabbed if in fact it was grabbed by one of the controls managed by MTInnerWindow. This can create havoc in the subclass code depending on what it needs to do with touches.

[Mathieu Virbel]

It's a bug, it should be released.
Grab is also used in widget like MTKinetic. So yes, it's clearly a bug :)
Feel free to open an issue or send patch !

Thanks :)

2010/8/23 Jonathan Gossage <jgos...@gmail.com>: