# JBrowseReactLinearGenomeViewRootModel
Auto-generated @jbrowse/mobx-state-tree API for the current JBrowse release —
see [pluggable elements](https://jbrowse.org/jb2-staging/docs/developer_guide/) for concepts.
[View source](https://github.com/GMOD/jbrowse-components/blob/main/products/jbrowse-react-linear-genome-view/src/createModel/createModel.ts).
Composes the shared EmbeddedRootModel with a LinearGenomeView session plus the
LGV-only `disableAddTracks`/`height` props.
## Properties
| Member | Description |
| --- | --- |
| **disableAddTracks**
disableAddTracks: types.stripDefault(types.boolean, false) | |
|
menuBar: types.stripDefault(types.boolean, false) | Draw the app-shaped `File` menu bar above the view. Off by default: an embed is the chrome a host asked for, and this is a component that has never had an application's bar. |
| **height**
height: types.maybe(types.string) | Any CSS height, applied to the component's own root whether or not a drawer is open. Absent, the component is content-height and grows with the page, and the host's box is what bounds it. |
| **drawerViewHeight**
drawerViewHeight: types.stripDefault(types.string, '100vh') | Superseded by `height`, which does the same thing without the "only while a drawer is open" condition. Still honored when `height` is absent. |
## Getters
| Member | Description |
| --- | --- |
|
() => { label: string; menuItems: MenuItem[]; }[] | The height in force: `height` when a host gave one, `drawerViewHeight` while a drawer is open, and nothing otherwise -- the view is content-height and the host's own box is what bounds it.
One definition with two readers, and the second is why it is here rather than in the component: a bounded view is exactly the case where pinning the header means something, so the session's `stickyViewHeaders` reads this too. #method One `File` menu, and only the two items an embed can honour: it can open a track or a connection into the session it was handed. The app's own File menu also starts, imports and exports sessions, which here would let a reader discard the view its host configured with no route back -- and `Add`/`Tools` have nothing to hold when there is one view and no plugin store.
Empty unless `menuBar` asked for it, and empty under `disableAddTracks` even then: both items are the add-track affordances that option exists to remove, so what would be left is a bar of rows the session guards refuse. The bar draws nothing for an empty menu set. |
| **effectiveHeight**
string | undefined | |
## Methods
| Member | Description |
| --- | --- |
|
() => { label: string; menuItems: MenuItem[]; }[] | #getter The height in force: `height` when a host gave one, `drawerViewHeight` while a drawer is open, and nothing otherwise -- the view is content-height and the host's own box is what bounds it.
One definition with two readers, and the second is why it is here rather than in the component: a bounded view is exactly the case where pinning the header means something, so the session's `stickyViewHeaders` reads this too. One `File` menu, and only the two items an embed can honour: it can open a track or a connection into the session it was handed. The app's own File menu also starts, imports and exports sessions, which here would let a reader discard the view its host configured with no route back -- and `Add`/`Tools` have nothing to hold when there is one view and no plugin store.
Empty unless `menuBar` asked for it, and empty under `disableAddTracks` even then: both items are the add-track affordances that option exists to remove, so what would be left is a bar of rows the session guards refuse. The bar draws nothing for an empty menu set. |