| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: 7048633
Change-Id: I85d4780286a663ab75555049f21b7215e45870d0
|
|\ |
|
| |
| |
| |
| | |
Change-Id: Ib072508c9e00f5ac227bda89b943e217292d9640
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A previous commit (2c57cbea0d663b) introduced support for
running Junit tests concurrently on all connected devices.
It relied on changing the TestIdentifier to store device
information, and having a single listener that listens to
test events from all devices.
The change to TestIdentifier caused issues with some users
of ddmlib in cases where the device info is not available
all the time.
This patch reverts all the changes in ddmlib, and moves
the knowledge of what device tests are being run to the
listener layer in ADT. So now we have a per device test
listener that knows only about tests run on that device.
Change-Id: Iffedcb38cdf21e349fbe38ecf9a654060b469b04
|
|/
|
|
| |
Change-Id: I41a8414669ba82f6053d2f5b7d582dbf32ba6e72
|
|
|
|
|
|
|
| |
Move stuff out of sdklib into common and ide_common.
Remove androidprefs and move the one class into common.
Change-Id: I71d126a13cf2ba413692e29616f4968a37d7b33a
|
|
|
|
| |
Change-Id: I2983399832a8f64b8ac0447587233baba4774311
|
|
|
|
| |
Change-Id: I7e949a943694a98faab5aa475808f4f071e1ade4
|
|
|
|
|
|
|
| |
Add ampersand to the list of characters that need to be escaped.
Fix for http://code.google.com/p/android/issues/detail?id=34138
Change-Id: I48bdece34d41b713b3f61211528faaedc9a2b40f
|
|
|
|
| |
Change-Id: Ie085ec76f9033d50acf086b89748e764b33f5f0c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently we allow launching an activity on multiple devices
from a single launch configuration. This CL adds support for
running Junit tests on all connected devices/emulators from
a single launch config.
At the UI level, all test results now show up as children
of per device test suites.
The changes are primarily in 3 different areas:
- In ddmlib, the main change is to save the device name
on which a particular test was run. This information is saved
in the TestIdentifier that is created per test case.
- In ADT, the general launch action (IAndroidLaunchAction) is
modified to support launching on multiple devices. This simply
loops over the existing launch action for each device for
Activity Launch or Empty Launch. The Junit Launch Action
is modified to launch a single Junit UI and collects the
results from all devices and passes it on to the Junit UI.
- ADT's ITestRunListener's are modified to look at the device
on which a test was run and add results in the appropriate
per device test suite.
Change-Id: I936c2db2398fcad16544794441dedc714de9bea8
|
|
|
|
| |
Change-Id: I6238185edd10227a01ae2f5282de18b17edb26bc
|
|
|
|
|
|
|
| |
Fix NPE that could happen if the device goes offline even before
logcat command is issued on it,
Change-Id: I334caae5e42d25eff396ce0b7b7a5e44c3ed4f61
|
|
|
|
| |
Change-Id: Ib7b0ee2986d2a7273a23c2e3d6c7a0aa7afc20fb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are a number of places where we need to display a device
name. Currently, DDMS shows the serial number + manufacturer/model
if available, but in other instances, we just show the serial
number.
This CL provides a getName() method in the IDevice interface so
that all the locations which require a human readable name can
use this.
The name is typically of the form manufacturer-model-serial.
If the manufacturer/model strings are not available, then those
fields are omitted, so it will show just the serial number.
Change-Id: I80ef7b48a4c7c8587042c1227c932251e18dba2e
|
|
|
|
|
|
|
|
|
|
| |
This CL allows the default action to be either of the "Find Next"
or the "Find Previous" buttons in the find dialog.
Typically, in logcat you want to find previous, while in gltrace
view you want to find next.
Change-Id: Ie11cbd8a7987b8011ec2ee3664034e9ecfc4e24b
|
|
|
|
| |
Change-Id: If2e89c894f5f11104e30d892bcae2b2daec17b08
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Related emulator change: 733fffaac9ccebfc424fccf9467b22475f71a2f8
Change-Id: Ie7948a9be6c1289306968cda91d1e0f0cf7cb61c
|
| |
| |
| |
| | |
Change-Id: Ie3b2e424a7dc9df73aca1c7914497f1c9a126901
|
| |
| |
| |
| | |
Change-Id: I137994ea4723299461c695559d664230a98b082f
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This CL adds support for invoking a find dialog when
the logcat view is in focus. The dialog can be invoked
via Edit -> Find (Ctrl + F), or via the context menu.
The dialog provides a way to specify a search term and
allows the user to search forward or backward in the
list of messages.
Change-Id: I7e7c6b20a051c161f035b3b45aba5f119f2c11a9
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I3825ba3149c644e834744f347a3973e9c8cd07ce
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
First, update our various project-specific Eclipse compiler settings
configuration files to include the new Eclipse 4 flags.
Second, turn off the "Unchecked conversion from non-annotated type to
@NonNull" warnings; there are hundreds or thousands of these, and
there isn't much we can do about them when they're coming from
platform and library APIs.
Third, make the lint projects warning-clean again by addressing
various warnings Eclipse found (such as some unclosed resources and
some null handling issues; yesterday's null annotation fixes only
addressed errors, not warnings.)
Change-Id: If75f7401a1cbeef1bf58b47ccaa9ad17bede7f91
|
|/
|
|
|
|
|
| |
This changeset fixes various code fragments opening
resources without closing them.
Change-Id: I6ed48a32dc5de4c11cab394dd3883ebbb54d2938
|
|
|
|
|
|
|
|
|
|
| |
This patch enables users to customize the colors used for
log messages of different priority levels. These settings
are available in the Android -> Logcat -> Colors preference page.
This fixes: http://code.google.com/p/android/issues/detail?id=31494
Change-Id: I9430f573f84f09d00bfe25d6e53eeccf4e338e9d
|
|
|
|
|
|
| |
SDK Bug: b/6043405
Change-Id: I2c189ef30d68738de8becff874343296ad9c412b
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To help users who don't know about logcat, we automatically monitor
logcat output to see if there are any errors from a user application,
and if so, display the logcat view.
This patch makes this feature a bit easier to use:
- The first time the logcat view is about to be displayed, a dialog
is shown that allows the users to enable/disable auto monitoring.
Note that this can also be done via logcat preferences.
- Users can now control the message priority that will trigger
auto monitoring.
- Once the logcat view has been displayed, we turn off auto monitoring
until the next launch. This reduces overhead and avoids unnecessary
change of focus in cases where the user is already interacting with
the logcat view.
Change-Id: I44a9ccea9148dea7bf6dc7d7864a1bb56a7376fe
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, when users create regex based filters, any error in the
regex pattern is logged. When the error is logged, context switches
to the Eclipse console view. As a result, users have to switch back
to the logcat view and fix the error.
This patch validates the text on entry and sets the text color to
be red if the pattern is incorrect. There are no context switches
as a result.
This fixes issue: http://code.google.com/p/android/issues/detail?id=22019
Change-Id: I5b571e34c1517b0a78046b56ad83c2aa8632abdb
|
|
|
|
|
|
|
|
|
|
| |
When a device is disconnected, an explicit message informing
the user of this event is attached to the log.
See http://code.google.com/p/android/issues/detail?id=25830 for
the reason why this might be useful.
Change-Id: I969004cb72b877b8319a639607f82c1c9f9a8635
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch allows users to create logcat filters based on an
existing message. When a message is right clicked, it brings up
a menu with an entry that says "Filter similar messages..".
Selecting that will bring up the "Add new filter" dialog with
its input fields prefilled based on the message contents.
This fixes: http://code.google.com/p/android/issues/detail?id=25835
Change-Id: If324330cbf78b503be61c31ebcff053d0f869c1e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch fixes a bunch of outstanding issues related to
scrolling in the presence of a full buffer.
Currently, the logbuffer is provided as the input model to the
TableViewer, and ViewerFilter's are used to filter the data.
This patch removes the JFace toolkit and directly works on the
SWT Table. When log messages arrive, rather than refreshing the
entire table, we can now just delete the TableItems corresponding
to the logs that were pushed out, and add new TableItems for the
incoming logs.
At steady state, this implementation performs far less work than
the previous implementation. However, during startup, this
implementation will perform more work since it does not use the
SWT.VIRTUAL bit (as all TableItems are created anyway).
Also, zebra striping has been removed to avoid appearance of flicker
when scroll lock is on.
Auto scroll lock behavior has been removed, and scroll lock button
behaves exactly like the scroll lock button in an Eclipse console.
Change-Id: Ic14487f7ad41338a581aed0ba2d85d292a584950
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Issue: http://code.google.com/p/android/issues/detail?id=28253
Change-Id: If7b3c2a898b30834a8e76c5aad615a41ba5ecc04
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
swt.jar must be found relative to the out/ dir
(as generated by create_all_symlinks.sh) to avoid
setting a platform-specific path.
swtmenubar was missing the new libs references.
Change-Id: I365cfa6e011ec831c4df87cb36b0df722caac2e4
|
| |
| |
| |
| |
| |
| |
| |
| | |
The whitelist doesn't seem to serve any purpose currently, but does
prevent legitimate attempts to access paths that aren't in the whitelist.
Bug: 6325674
Change-Id: I0fbd44bb440a2b28010a9ca5c5ebd625130de628
|
|\ \
| | |
| | |
| | |
| | | |
* commit '7312c89ade9495d42132ec7fdf7db8142da5fa8a':
Ensure screenshots saved through DDMS end with .png.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This patch simply makes sure that the filename will have a .png extension when saving a screenshot through DDMS.
Change-Id: Idb00259ac456fcaf11ee99736663fc7ddbbc505b
Signed-off-by: Sebastian Roth <sebastian.roth@gmail.com>
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | | |
* commit 'c2d5ffe0b9baa1c24a62459b82bb21df08f4250b':
Add support for the WindowBuilder Property Sheet
Switch libraries from Eclipse 3.4 to Eclipse 3.6.2
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit f3d3fa912a10e20cadae813b80a66e538f77131d.
Change-Id: I72e28e21db3c7f959040c1fbb9df14e4d85d0df4
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* commit 'c12302ae5385828ce385d90c49c69cad504dd98d':
Update classpath for eclipse project due to prebuilt move.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Don't use User Libraries. It's easier to just hardcode them with
a classpath variable.
Change-Id: If8c1236199dd6766d48cf9b553fa2a9ee0d236e6
|
|/ /
| |
| |
| | |
Change-Id: If39d1d21baef72cdd2a8a0f2ced1ebbe6e02c891
|
|\ \ |
|
| | |
| | |
| | |
| | | |
This reverts commit b0c819f896b3c579633849e3fa674a30e6978dd7.
|
|\ \ \
| |/ /
|/| | |
|
| |/
| |
| |
| |
| |
| | |
Done to allow reuse.
Change-Id: I7a0651bb66e51997b08af7f46b8db4da7c9a0fbf
|
|/
|
|
|
|
|
|
|
|
|
| |
This updates the org.eclipse.core.command, org.eclipse.jface and
org.eclipse.equinox libraries from Eclipse 3.4 to Eclipse 3.6.2.
It also updates SWT from 3.4 to 3.6.2 (and this drops the Carbon
support from the SwtMenuBar library since SWT 3.5 switched to Cocoa by
default.)
Change-Id: I7e8a6e3b8cb473f90eca3b90e3f3dc5fa5099b71
|
|
|
|
|
|
|
|
| |
The thread id's output in "logcat -v long" used to be encoded in hex,
but not anymore. This fixes the logcat parser to accomodate both the
old and the new formats.
Change-Id: I0871a68f2f82c5e4660c404ec8970063d7b68a88
|