may be help: http://android-er.blogspot.com/2011/09/onsaveinstancestate-and.html
On Oct 8, 4:45 am, King Salamon msalamon.comcast@gmail.com
wrote:
Please can anyone give me a full coding example for getting data to persist
after the device is rotated. All of my textView fields go back to
This does not work for textView
see Kostya's post above
And IIRC, TextView by default doesn't save or restore state even if
there is an ID
On Oct 8, 11:14 pm, decode decode.develo...@gmail.com wrote:
Give an id to your textview. Android system should handle it...
On Oct 9, 8:35 am, Studio
Thank you everyone for the great insight on this issue. I tried the
simple -down and dirty workaround by adding
android:configChanges=orientation|keyboardHidden
to the activity tag in the manifest. This did in fact work as the data
persisted after rotation.
However, as many have pointed out, this
Setting
android:freezesText=true
in the layout XML forces a TextView to save its content. The view needs
to have an ID as well.
-- Kostya
10.10.2011 17:48, King Salamon пишет:
Thank you everyone for the great insight on this issue. I tried the
simple -down and dirty workaround by adding
Excellent --this works! Thanks
On Oct 10, 9:54 am, Kostya Vasilyev kmans...@gmail.com wrote:
Setting
android:freezesText=true
in the layout XML forces a TextView to save its content. The view needs
to have an ID as well.
-- Kostya
10.10.2011 17:48,KingSalamonпишет:
Thank you
09.10.2011 2:41, Studio LFP ?:
*TreKing, Kostya, Romain Guy,*
I do understand what you guys are saying, so I am listening, but it
seems to be a contradiction since it seems most of the internal
applications use it, including quite a few that Google themselves send
with the devices.
I'm compiling a list of things that need to happen in both cases. So far it
looks like a lot bigger challenge to not use the android:configChanges than
to use it.
I've read the optimization post plenty of times and do understand it, but
I'd like to get the big picture for the usages of both to
On Sun, Oct 9, 2011 at 10:59 AM, Studio LFP studio@gmail.com wrote:
3. Special consideration now has to be taken with AsyncTasks since they are
linked to the UI and need to be stopped, location of processing saved and
restarted
False. Special consideration may be required but they do not
On Fri, Oct 7, 2011 at 3:59 PM, Studio LFP studio@gmail.com wrote:
Add this to your activity tag in the AndroidManifest.xml
android:configChanges=orientation|keyboardHidden
That will fix you up
That will hide the issue until the app is destroyed / recreated via some
other means - like
*TreKing,*
This is true, but he didn't ask about that. He just asked about a way for
an EditText to keep the text it has on a rotate.
The easiest and fastest way to solve that particular problem is the
configChanges XML attribute.
You'll note that I said their may be a need for other options
On Sat, Oct 8, 2011 at 12:00 PM, Studio LFP studio@gmail.com wrote:
*TreKing,*
This is true, but he didn't ask about that.
LOL - so since he didn't ask for for a method that covers the case I
mentioned, it's OK to give him a limited solution?
He just asked about a way for an EditText
*TreKing,*
If you choose to ignore a well documented feature given to us by the Android
team, that's your prerogative. As for the rest of us, we'll decide when we
prefer to use one feature over another.
*King Salamon*,
As stated previously, regardless of which way you choose to do it
On Sat, Oct 8, 2011 at 4:02 PM, Studio LFP studio@gmail.com wrote:
*TreKing,*
If you choose to ignore a well documented feature given to us by the
Android team, that's your prerogative. As for the rest of us, we'll decide
when we prefer to use one feature over another.
Which well
*TreKing,*
If you choose to ignore a well documented feature given to us by the
Android team, that's your prerogative. As for the rest of us, we'll decide
when we prefer to use one feature over another.
He makes a good point. Solving this issue by requesting to handle
orientation changes
The user changing the language is a config change (likely rare, except
for developers testing localization, but still).
Possibly more commonplace, docking (and undocking), is a config change.
Back to the original topic: Andorid automatically saves and restores
those views that have an ID. If
*TreKing, Kostya, Romain Guy,*
I do understand what you guys are saying, so I am listening, but it seems to
be a contradiction since it seems most of the internal applications use it,
including quite a few that Google themselves send with the devices. Maybe
they aren't, but based on the speed
On Sat, Oct 8, 2011 at 5:41 PM, Studio LFP studio@gmail.com wrote:
I do understand what you guys are saying, so I am listening, but it seems
to be a contradiction since it seems most of the internal applications use
it, including quite a few that Google themselves send with the devices.
Thanks for the link there. I've read that a couple of times and understand
the uses.
Is there a set of documentation that tells what is automatically saved off
if you don't use the configChanges option? I know a little by catching it
here and there on these groups, but I haven't located a full
Give an id to your textview. Android system should handle it...
On Oct 9, 8:35 am, Studio LFP studio@gmail.com wrote:
Thanks for the link there. I've read that a couple of times and understand
the uses.
Is there a set of documentation that tells what is automatically saved off
if you
Add this to your activity tag in the AndroidManifest.xml
android:configChanges=orientation|keyboardHidden
That will fix you up unless you have some other specifics set like different
XML layouts for portrait and landscape. If you do, you may want to use the
bundle or just change the view
20 matches
Mail list logo
