- Labels have typography consistent with the rest of Winscope
- Fix labels position - get rid of fragile hardcoded x-axis shifts
Fix: b/251785717
Test: run "npm run start", load SF trace, check layers labels
Change-Id: Id32b31f3bf66e4096fedfb3369f6df479f4e0c47
- WindowManager viewer
- IME viewers
Fix: b/254437771
Test: load WM + IME traces in winscope, click on an entry in the hierarchy view, check that there is no blank space in the properties view between controls on top (filter) and the properties (tree) view below
Change-Id: I943433b594e91d4d6323af50087002b42d324d40
The field is not registered as an IntDef but uses the same values as
LayeoutParams according to code codumentation
Test: npm run test:all && open a layers trace and check if
inputWindowInfo has a value and if the flags are correctly formatted
Change-Id: I868e1b3088cf9925c50faf0decce2da1f584288d
In case of repeated/equal timestamps, the first occurrence is the search's result.
Test: npm run build:unit && npm run test:unit
Change-Id: If15a7c815c654a3c6ad53c6626b9a89fcb536bff
Layer types are deprecated.
Test: open traces with winscope and check buffer info is visible
Bug: 238781169
Change-Id: I1f1aeae4e86a2d44a7125dd03d31271d1b143a75
Test: run idegen.sh to generate files for IntelliJ without error
Signed-off-by: utzcoz <utzcoz@gmail.com>
Change-Id: If1066d236ef44aff6b9f73a40751ad232a80f6f9
Add extra properties to IME viewers from the IME traces and SF/WM
traces.
Bug: b/238088679
Test: npm run test:all
Change-Id: I177fc7353f963cc8b1391a88d5d8f4b2e4f387fa
IM Clients, Service and Manager Service viewers - not yet including new
WM/SF combined properties view in hierarchy.
Bug: b/238088679
Test: npm run test:all
Change-Id: I4bd05ca5dff14abbf6d3a89b0e07730233edf1b0
Refactor tree utils for proper reuse from IME viewers:
- add common/trace/trace_tree_node (factored out from viewers)
- rename renaming viewers/common/tree_utils -> viewers/common/ui_tree_utils
- add common/utils/tree_utils: generic tree utils reused from "trace" and "ui"
Bug: 238088679
Test: npm run build:all && npm run test:all
Change-Id: Ib14dd3495dc7e91e3a0eef2fdc20efa27fe1ef2e
Test: run idegen.sh to generate files for IntelliJ without error
Signed-off-by: utzcoz <utzcoz@gmail.com>
Change-Id: I80958e94f93a8e1ef546bc34bd929d04a224dc9e
Rect labels are clickable. Pan added via right click and drag, zoom added via scroll.
Bug: b/245914589
Test: npm run test:all
Change-Id: I49ffd26b1c735390960e6b523acf3070951c903d
Creating WM viewer and refactoring some of the generic components to
ensure their re-use.
Bug: b/238086082
Test: npm run test:all
Change-Id: Ib47a7c96f8966f642ef947ac5c35abb60dfff569
Test presenter separately to ensure ui data properly updated after each
public method. Test tree transformer. Extend tests for tree generator.
Test trace coordinator.
Bug: b/238089034
Test: npm run test:unit
Change-Id: Icf7770f3310d39903f42c7b12e030946afd6cd14
In addition to above, refactored some of the typing so that File rather
than Blob is used by the parsers.
Bug: b/244297039
Test: upload zip file attached to trace
Change-Id: I85918fdd2640f249dbc7c8a69c8a3d63a34d26d1
Update to match figma designs for the viewer section - app toolbar, tabs
for different viewers, etc.
Bug: b/244715720
Test: npm run test:all. also upload any trace to see what it looks like
Change-Id: I85b64e4a660fd30c6d71eb8ef3cb3b45c37a2943
The previous protobufjs version had a bug that triggered an exception while loading/decoding SF state dumps.
Test: capture Surface Flinger dump as follows
- Enter PiP, e.g. start maps navigation and exit the app
- Press on the PiP window to make the PiP menu appear
- Dump state SF in winscope
Change-Id: I33ea12f681ce8b8b95f78df3454db687beffb9d7
Created the viewer component for SF traces, including rects view,
properties view, hierarchy view (for re-use in other apps). This CL
contains properties view and changes to associated reusable components.
Currently follows same design as go/winscope-beta.
Bug: b/238089034 b/232081297
Test: npm run test:all. upload/run any SF trace to see what it looks
like.
Change-Id: I6f9f0b1002ab9901f1aee113cbb0fef4cbd078a6
Webpack 4.46 is not compatible with node 18.6.0's openssl and this commit introduces
the unsecure workaround of specifying NODE_OPTIONS=--openssl-legacy-provider
Note: we can't easily upgrade to webpack 5.*, because some dependencies
(e.g. Kotlin/JS webpack plugin) are incompatible with Webpack 5.*
Test: yarn build
Change-Id: I0a367ece0d6e9bf39f9bbc8709527f47064e4dd3
Created the viewer component for SF traces, including rects view,
properties view, hierarchy view (for re-use in other apps). This CL
contains hierarchy view and associated reusable components.
Bug: b/238089034 b/232081297
Test: npm run test:all. upload/run any SF trace to see what it looks
like.
Change-Id: I3dd7c3f73ac7d7dac9b65d5fc7853e9fc8b8e56e
