Skip to main content

In iOS, Is GestureRecogizer target action running in a separate thread?



Here is the problem, on the UI of my iPhone app, I have a button and another imageView that accepts Touch gesture recognizer, both have target actions. If I touch the button and the view one at a time, everything is fine. But if I touch these 2 simultaneously, or in rapid succession, things get messed up. The button and gesture handler manipulate the same state variables, so if they run side by side, the result is non-deterministic.





I tried to fix this problem by disabling the button the instant I get into gesture recognizer handler, and enabling it right before exiting the handler. But this doesn't solve my problem!!!





So the only possibility (my guess) is that the gesture recognizer gets triggered when the button handler is running. But this could only happen if they resides in separate threads. So does anyone know if the gesture recognizer handler is running in a different thread? Or, more specific to my problem, what should I do in my situation? Use guard variables to prevent conflict?


Comments

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex