![]() The button (or any element) was not clicked by the touch interaction.īelow is my code. However, it seems that the touch interaction does not take place at a certain coordinate. After the gesture is dispatched, turn on the overlay again. My potential solution right now is before dispatching gesture, turn off the overlay. TableRow TableLayout table row add delete remove removeview addview get table row index indexOfChild create table row dynamically TextView dynamically. Since the overlay object will intercept touch interactions, if I simply dispatch the gesture, the confirmation dialog will appear over and over again. What I want is after users confirm an interaction, my app will perform that action/interaction on behalf of users. The overlay view is used to capture user interactions and confirm the caught interactions with users. import, I work on an android project related to recording and replay.Just upload the code and pull out WindowManager, a small Demo: Haha, don’t spray, I want to removeView but I want to be there, do whatever I want, outside the life cycle of Activity~ The effect we want to achieve is: click to display Button-addView, click to eliminate Button-removeView, In fact, there is no need to elaborate on how many holes it has, just avoid these holes.Īfter this period of project development, summarize a truth:ĭon't write stuff in things like Activity, which has a life cycle, or it will be destroyed inexplicably, and then built, but it is already a matter of fact, and the end is abnormal status, null pointers and various Crash pits. ![]() ![]() Today we will take a look at the pits of removeView in WindowManager. As the saying goes, developers who have not encountered similar not attached to window manager and Android removeView view must not be null are not good engineers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |