| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Also fix the build file of the a couple of test projects.
Change-Id: I5e75f9c4ac397350d7b54e660782d38a2e3de5ad
|
| |\ |
|
| |/
|
|
|
|
|
|
|
|
| |
When using Device page > Create AVD, this will switch
the AVD Manager to the AVD page, refresh the AVD list
and select the new AVD.
SDK Bug: 38785
Change-Id: I7cff8f434b16d90cc9e46e938631e6b67bb69af7
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Also set default target if there's only one in the current SDK.
SDK Bug: 38785
Change-Id: I76d92ea4c43f94275f3d4373251a87ec3a6610a1
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| | |
Change-Id: I88d76329ab5f3afa4fda338c170a78bef1939165
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This should maintain compatibility with upgrading features provided
by ADT plugins.
Change-Id: I9a711fd0a9239cfeea421919a2789c82a93899da
|
| |\| | |
|
| | | |
| | |
| | |
| | | |
Change-Id: I521d25a68cd80444bc58f08c4b3939501197517d
|
| |\ \ \
| |_|/
|/| | |
|
| | | |
| | |
| | |
| | | |
Change-Id: I3e59f7880afce36c3ee1195e0927d43208c5c4e1
|
| |\ \ \ |
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The bug happens when the SDK Manager is open using the embedded
class from within Eclipse 4.2 -- the SWT used is then the newer
3.7 which doesn't have the same cocoa interface for menus.
The fix is threefold:
- If the cocoa enhancer fails, revert to the generic one. This doesn't
quite help here since the crash is actually when the native handler
is invoked but the setup is fine.
- Implement a new enhancer on top of the newer SWT 3.7 APIs that lets
us access the About and Preference menus on Mac. That was the whole
point of the enhancer workaround since SWT 3.5 an 3.6 don't have
access to these menus directly. This new enhancer is used if SWT
version 3700+ is used on Mac.
- Finally the crash only happens when using the embedded version of the
SDK Manager within ADT. When possible this uses the forked
standalone version. It will still revert to the embedded one if ADT
is started without any tools.
The new enhancer for 3.7 on Mac is sub-optimal: since it *adds*
a listener to the about/preference Mac menus, that means when it is
invoked from within Eclipse these menus will generate 2 events,
e.g. bringing both the Eclipse preferences and then the SDK Manager
preferences. To support this case properly, we should detect this
runs from within Eclipse, not change the about menu and instead
integrate the sdk manager pref as a panel in eclipse's prefs. A
cheaper workaround is to revert to the default generic enhancer
that will create an options menu. Maybe for a later CL.
SDK Bug: 38640
Change-Id: Ib1588e401616548a5dc9eb216d3c35b579d3950b
|
| |\ \ \ |
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When formatting, peek at the model base location, if known, and if a
corresponding file is found which isn't in an Android project, use the
builtin Eclipse formatter instead. This should reduce the impact of
the Android XML editor registering itself for the xml content type and
affecting unrelated projects, at least in terms of formatting (which
is more severe than say additional completion options or extra go to
declaration targets.)
See issue 38747: Android Tools XML formatter with pom.xml
Change-Id: Ifa0e8527b7020c2ca4f477d6e0be6397d2dbdeff
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This changeset adds a new option, on by default, which causes the
layout editor to always pick the best rendering target. The best
rendering target is typically the most recent one. This option can be
toggled in the rendering target drop down menu (but it applies
globally), and choosing a specific rendering target turns it off.
Change-Id: I53e48a38741f364f2b68525a4898aca69b1ae7b1
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I93154fbe3c0d86b6767ef2283ecbc5038163c604
|
| |\ \ \ \ \ |
|
| | | |_|/ /
| |/| | |
| | | | |
| | | | | |
Change-Id: Ia00b9d6de3feb1b3dc99b8293c456e5b26e1b860
|
| |\ \ \ \ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When you have a field initialization like this:
private int foo = new ForbiddenClass();
the actual code to perform the initialization lives in a method named
<init> (or for a static field, <clinit>).
If you tried to suppress lint errors here by adding an annotation on
the field, it would not be found by lint, since lint looks at method
level annotations and it's sitting on the field node instead.
To fix this, the suppress check needs to identify the field scenario,
and in that case (when checking whether an error is suppressed) look
up the field in the class and check annotations there.
There was a second bug: The lint check which looks for invalid
suppress annotation sites (since they're not allowed on local
variables for class based lint checks) incorrectly concluded that
these types of initializations were local variables rather than field
initializations.
This fixes issue
38626: ADT: Misleading lint rule: SimpleDateFormat
Change-Id: I254f3fb5a6132d6cbe39bd425ffe6d67ed7b84ed
|
| |\ \ \ \ \ \
| |_|/ / / /
|/| | | / /
| | |_|/ /
| |/| | | |
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This changeset fixes a number of bugs with multi configuration
editing; especially around configuration switching and inheritance, as
well as some memory improvements.
It also synchronizes values between layout variations. If you for
example have layout-land/foo.xml and layout-port/foo.xml and you
change the Theme to Theme.Holo or the device to Galaxy Nexus, the
configurations for both files will be updated (whether or not the
files are open), and provided of course the layout folder doesn't
contradict it; layout-xlarge/foo.xml would be unaffected by the above
edit since Galaxy Nexus doesn't match the layout-xlarge folder.
Change-Id: I5c01555aad8339f68788d8aed1f707d30993ae1b
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I30db5f7fb88f3e422a507a0d49152c23f0dff4ff
|
| |\ \ \ \ \
| |/ / / /
|/| | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: Id110d90b173d052b952f90622bcbff64f5bedbe5
|
| |\| | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: Ia815a807db6d9b65f7852a4b8ae614fc69f510fe
|
| |\ \ \ \ \
| |_|_|_|/
|/| | | | |
|
| | | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Updated the groupId of most artifacts to be more
reflective of their sub-projects status in the SDK tools.
Added lint artifacts.
Change-Id: I900a165647a9b7d3c55b473f63c4ca4469762d7b
|
| |\ \ \ \
| |_|/ /
|/| | | |
|
| |/ / /
| | |
| | |
| | | |
Change-Id: I7a2d51324e97ceb6fb038b10bc382fa8da826d91
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | | |
Change-Id: Ic44f7e1fdc09d278ed3d6163a3ee6022b6a9dc69
|
| |\ \ \ \
| |_|/ /
|/| | | |
|
| |/ / /
| | |
| | |
| | | |
Change-Id: I9191826e7c764032b2c0075108b49f715fff3181
|
| |\ \ \
| |_|/
|/| | |
|
| |/ /
| |
| |
| | |
Change-Id: Iae39e23f6c72f5a2e1444c39da1eb1a78894e9f4
|
| |\ \ |
|
| | |/
| |
| |
| | |
Change-Id: Iead02d468590407ec274357f1a1c57ed8d5cc24c
|
| |\ \ |
|
| |/ /
| |
| |
| | |
Change-Id: I069f9df1c50cf16329934046ed1bc5bbd04d2533
|
| |\ \ |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix the handling of \r characters in the code which applies
formatting deltas into existing documents. It could end up
inserting the formatted portion in the middle of a \r\n pair,
which made Eclipse extremely confused
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=375421)
This fixes
32849: Eclipse android adt xml editing artifacting (unsynced) lines of
text when changes are made in the graphical interface
It also adds a lint check to identify *existing* files that already
have these mangled line endings, along with a quickfix to make the
correction.
Change-Id: I1e7024f2786e4cb0233c2c6b98c3d3f942703ea0
|
| |\ \
| |/
|/| |
|