Dotplot1DView
Auto-generated @jbrowse/mobx-state-tree API for the current JBrowse release —
see pluggable elements for concepts. Provided by the
dotplot-view plugin.
View source.
one axis of a dotplot. categorized General rather than View because it is not a pluggable view type, which the name-suffix heuristic would otherwise assume ref https://mobx-state-tree.js.org/concepts/volatiles on volatile state used here
Getters
| Member | Description |
|---|---|
dynamicBlocksBlockSet | this uses padding=false and elision=false |
| visibleRegions | The on-screen content blocks under the field names LinearGenomeView.visibleRegions uses, so this axis and a synteny row hand the shared comparative fetch window (syntenyFetchRegions) the same thing and the two displays' fetchRegions are one call each. Carries only what that window reads; the screen-px pair an LGV also exposes has no reader here, and deriving it would make this recompute with offsetPx. |
fitBpPerPxnumber | The zoom that fits this axis' whole genome, with a tenth of the axis to spare. Its own getter, separate from maxBpPerPx, because on a locked plot the two differ — see DotplotHView. |
maxBpPerPxnumber | |
minBpPerPxnumber | |
maxOffsetnumber | One rule at every zoom level: scroll until only leftPadding px of content remain visible on the right, or rightPadding px on the left.Deliberately NOT special-cased for content narrower than the view. Pinning both bounds to the centered offset there gives zoomTo — which clamps its anchor-preserving offset into [minOffset, maxOffset] — a degenerate range, so the cursor anchor is silently discarded and the plot snaps back to centered. That was the max-zoom-out "edge jump": the first zoom step displaced the locus under the cursor by the centered-vs-anchored gap, which grows with distance from center (~41px near the edge, ~0 at the center). center() still centers explicitly, so the initial view is unchanged. |
minOffsetnumber |
Actions
| Member | Description |
|---|---|
center() => void |