Closed mrkajetanp closed 1 year ago
Note: The current behaviour is to silently fail if the view doesn't match any of the activities found by SurfaceFlinger. I left that unchanged but I think it probably makes sense to add another check and throw a warning if the list is empty so that the user at least knows where the problem is coming from. I can update the PR if that's desirable to have.
All right I updated the PR, should be ready now :)
Change the SurfaceFlingerFrameCollector to match activities by prefix instead of looking for an exact match. This will allow to account for activities with variable suffixes. Raise an error if more than one activity matches the provided view.
Suggested-by: Andriani Mappoura andriani.mappoura@arm.com