Chet Haase c81a849388 Fix minor transition bugs and add capabilities
Some view changes require more flexible transitions than the
defaults provided by Crossfade and TextChange - this change supplies some
of that flexibility.

Also, starting a new transition on a hierarchy undergoing a transition
caused the first to get canceled, then the start values to be retrieved.
The new transition should actually get the start values from the intermediate
state of the views, so we now cancel the previous transition only after the
start values have been captured.

Issue #9756349 Transitions: Crossfade does not handle interruption/reverse correctly
Issue #9295863 Transitions: Add behavior API/flags to various transitions
Issue #9275859 Transitions: Improve mechanism for transition interruption

Change-Id: I5a8c5a12466ddcab9e84e4880930563fa1216f3b
2013-07-12 13:40:38 -07:00

61 lines
3.2 KiB
XML

<?xml version="1.0" encoding="utf-8"?>
<resources>
<string name="app_name">StatesTest</string>
<string name="states_test1">StatesTestv21</string>
<string name="states_test_auto_targets">StatesTestAutoTargets</string>
<string name="states_test_auto_transition">StatesTestAutoTransition</string>
<string name="states_test_auto_transition2">StatesTestAutoTransition2</string>
<string name="contacts_expansion">ContactsExpansion</string>
<string name="states_test3">StatesTest3</string>
<string name="states_test4">StatesTest4</string>
<string name="states_test5">StatesTest5</string>
<string name="states_test6">StatesTest6</string>
<string name="button">Button</string>
<string name="searchButton">Search</string>
<string name="searchText">This is some text</string>
<string name="resultsTitle">Search Results</string>
<string name="placeholder">Blah Blah Blah</string>
<string name="username">Username:</string>
<string name="password">Password:</string>
<string name="retype">Retype:</string>
<string name="new_user">New User?</string>
<string name="incorrect_password">Incorrect password:</string>
<string name="try_again">Please try again.</string>
<string name="login_successful">Success!</string>
<string name="first_activity_screen">First activity screen</string>
<string name="username_taken">Username taken:</string>
<string name="cancel">Cancel</string>
<string name="submit">Submit</string>
<string name="okay">Okay</string>
<string name="reset">Reset</string>
<string name="fadingButton">Fading Button</string>
<string name="removingButton">Removing Button</string>
<string name="invisibleButton">invisible Button</string>
<string name="goneButton">Gone Button</string>
<string name="start">Start</string>
<string name="toggle">Toggle State</string>
<string name="someText">This is some text</string>
<string name="shortText1">This is some short text</string>
<string name="shortText2">Not much text here</string>
<string name="longText1">This is the beginning of the Spring of my discontent. In the event of a real emergency, you would be notified by email. Fear not, for death comes swiftly.</string>
<string name="longText2">When do we get to eat? I like all things, especially following strong leaders, and mangy cats. Break glass in emergency. The purpose of a framework is to provide the facilities and functionality of a powerful toolkit with the simplicity of a refrigerator.</string>
<string name="state1">State 1</string>
<string name="state2">State 2</string>
<string name="state3">State 3</string>
<string name="state4">State 4</string>
<string name="button0">Button 0</string>
<string name="button1">Button 1</string>
<string name="button2">Button 2</string>
<string name="button3">Button 3</string>
<string name="button4">Button 4</string>
<string name="button5">Button 5</string>
<string name="a">A</string>
<string name="b">B</string>
<string name="c">C</string>
<string name="reveal">Reveal</string>
<string name="crossfade">Crossfade</string>
<string name="inout">In/Out</string>
<string name="textfade1">T1</string>
<string name="textfade2">T2</string>
</resources>