Package-level declarations
Types
A running native screen capture. Created by installAutographNativeScreenCapture; keep it to uninstall.
A running native tap capture. Created by installAutographNativeTapCapture; keep it to uninstall.
A scope declared with Fragment.autographScope or ComponentActivity.autographScope. Keep it to revise the properties; dropping it changes nothing, since the declaration is bound to the surface's lifecycle, not to this handle.
Properties
Declares that the fragments in this view's subtree sit beside their Activity's content rather than replacing it — a mini-player, a banner, a widget slot — so the Activity stays a screen of its own while they are attached (#281).
Marks this view and everything under it as excluded from native tap autocapture — the View counterpart of Compose's Modifier.autographIgnore().
Functions
Declares scope properties for the taps captured in this Activity: on its own views, and in every fragment and Compose AutographProvider inside it, each of which may declare its own scope on top (the inner value winning a key clash).
Declares scope properties for the taps captured in this fragment only — a detail screen's item id, a list's variant — the native counterpart of autograph-compose's AutographScope (#239).
Starts reporting native Android screen transitions: on every Activity or Fragment that comes to the foreground and names a screen, a Screen Viewed event is emitted via tracker and a screen frame is pushed onto scopeStack so autocaptured events on that screen carry it; the frame stops answering when the screen leaves the display. This is the Android counterpart of the iOS UIKit viewDidAppear: capture, sharing the same ScopeStack/ScreenHistory and so the same previous_screen chain across a Compose↔native transition.
Starts reporting taps on native Android View content (XML layouts, RecyclerView rows, legacy screens) as eventName. This is the Android counterpart of the iOS UIKit tap capture, and the pipeline autograph-compose cannot serve: Compose autocapture hit-tests the semantics tree, which does not see an android.view.View hierarchy at all.