aboutsummaryrefslogtreecommitdiffstats
path: root/layoutlib_api/tests
diff options
context:
space:
mode:
authorTor Norbye <tnorbye@google.com>2012-09-18 15:55:42 -0700
committerTor Norbye <tnorbye@google.com>2012-09-19 08:02:33 -0700
commit630d28af94d1d7f5f791e49d8504a16b7f4559a4 (patch)
treebec243a778f3a60a89e8730a5fb228728d78084f /layoutlib_api/tests
parent053a7903f1460d95e01ce609b3b998c4feac6d1d (diff)
downloadsdk-630d28af94d1d7f5f791e49d8504a16b7f4559a4.zip
sdk-630d28af94d1d7f5f791e49d8504a16b7f4559a4.tar.gz
sdk-630d28af94d1d7f5f791e49d8504a16b7f4559a4.tar.bz2
Improve last editor mode handling
We recently added the ability for the IDE to remember whether you last edited an XML file in text mode or in graphical mode (see issue 31340). However, this was tracked with a single boolean flag, which meant that it was an "all or nothing" flag. However, you may want to always edit string resource files with the XML editor, but you want to always use the graphical editor for the manifest file. In this changeset, the state is kept in a bitmask instead, which allows us to track the broad editor types separately. With this, new editors are opened according to the last mode you used for that type of editor. (Note that it tracks "categories" of editors, not individual resource types, so for example the editor for color resources and the editor for state list drawables share the same last mode as the string resource editor. This is because these editors share roughly the same graphical editing capabilities.) (The CL also contains some minor code cleanup.) Change-Id: I4624dffa2349230684c0558a33081adda8d799b2
Diffstat (limited to 'layoutlib_api/tests')
0 files changed, 0 insertions, 0 deletions