summaryrefslogtreecommitdiff
path: root/android/testData/render
AgeCommit message (Collapse)Author
2014-07-08Fix MenuPreviewRendererTestTor Norbye
Now that the test machines have android-L installed, layoutlib supports native actionbar/menu rendering, which provides better (and different) rendering, requiring the rendered master thumbnails (which are image-diffed as part of the test) to be updated. Change-Id: I5f802b17a6427afd7a209bb51e060bcbda9f836b
2013-11-01Fix render error panel to include non-framework unknown tagsTor Norbye
Fix the render error output such that it doesn't suppress core tags (e.g. tags without dots) if they aren't known ones. This helps you for example know that you cannot use <DrawerLayout>, you have to use <android.support.v4.widget.DrawerLayout> Change-Id: I0fd6fd08a21eb0cbaf6f0a8d6b3d3b6e948c2856
2013-10-23Add render preview support for drawables, menus and widgetsTor Norbye
This changeset adds render preview support for XML drawables, XML menu files, and XML widget files. Drawables should work accurately; menu previews are representative. As with layouts, selection between the editor and menu items are synced with the preview window. Change-Id: I97f4e857bc6285a1b0643aeb80b769825b543e4e
2013-09-04Improve render error stacktrace displayTor Norbye
This CL improves the way render errors are handled: 1) If the error is recognized to be due to the known layoutlib bug for CalendarView and DatePicker, then display a specialized error message rather than the corresponding stack trace. 2) There are some heuristics in the render error panel for cleaning up stack traces such that it only shows the relevant stack frames, and not for example the stack frames for the IDE itself as it called into layout lib. There were some bugs in this which meant that the above CalendarView stack trace was completely hidden. This was the topic of issue 57676. While that particular scenario is now handled with a custom message, this fix means any other similar exceptions in the future will show up with a relevant stack trace. 3) Add unit tests for a couple of different render error scenarios. Change-Id: Iffbab71b3ac593719bced193fc4c10e2f49c3b96
2013-05-02Add action to obtain a screenshot from the deviceSiva Velusamy
This CL adds a "Screen Capture" action to the Device Panel. When invoked, it obtains a screenshot of the currently selected device, and shows it in a screenshot viewer. The screenshot viewer dialog provides the following actions: - Capture the screenshot again - Rotate the captured image - Frame the image with device artwork. Optionally include drop shadows or a screen glare effect. The device artwork itself is a unmodified copy of whatever is available at http://developer.android.com/distribute/promote/device-art.html The JSON syntax comes from the same URL, but we can tweak this if necessary. Change-Id: Ib0760f798649fc9fe25c15a45cd802f892f80a9a
2013-03-20New render error handlingTor Norbye
This changeset replaces the error list in the layout render preview with an error panel near the bottom which is overlaid on top of the rendering (and is partially translucent). The error output is formatted HTML (similar to the code analysis details pane). There are hyperlinks to perform actions (also similar to e.g. how suppress works in the code analysis panel). The existing fixes were ported (e.g. configure SDK, or change compilation target from 1.7 to 1.6) and new ones were added, such as actions to insert all missing layout_width or layout_height attributes, checking missing class names for typos and offering to replace them with the correct spelling, building the project, creating a custom view class from an unknown tag, show javadoc, as well as diagnostic help such as identifying missing style errors and suggesting that the wrong theme might be chosen. Change-Id: I4f903af43473bf7f4b2e7d5b090d1ff385cb6f45