Skip to main content

What event Asus Transformer calls in Android, then docking or undocking the tablet?



I have problems with my app on Asus Transformer TF101, with keyboard.





If i dock it to keyboard (or undock it) during displaying a activity, the activity is recreated. That means: onDestroy is called. onCreate is called.





Is it possible to catch the event that user is undocking or docking?





I would like to show a warning message, save the data and finish the activity..





Problem background: In my case, it changes the data in edittext fields, then user undocks or docks. I have created a tablelayout with edittexts fields, like editable datagrid. On Asus it messes up, then undocking, the system recreates the activity and all data in datagrid is rewritten automagically. All rows become like the last row. I assume that system does the redraw by ID's, but i have inflated the rows into datagrid, so the edit fields in rows have same ID's.


Comments

  1. Try adding android:configChanges="keyboard" to your activity. See here and here for how runtime changes work with regards to Activities.

    On the other hand, if it's operating like a phone dock, then try listening for ACTION_DOCK_EVENT. See here for a tutorial. This would not explain why the activity is being recreated, though, while the above does.

    ReplyDelete

Post a Comment

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