Colin Diesh
Colin Diesh
can you post a couple session links that demonstrate the usage of this feature?
nice work...random test, I tried changing to "compact" features here but the height did not adjust to the new shorter height of the track after applying compact https://jbrowse.org/code/jb2/layout_max_height_calc/?config=%2Fgenomes%2FGRCh38%2F1000genomes%2Fconfig_1000genomes.json&session=share-aZWHI-8%2B%2Bu&password=uqy0x i originally...
@nathanweeks configuring the track height in config.json is already allowed in released versions, and it should remain allowed even after this PR :) an example of config.json with height preconfigured...
>will the default value for the "auto-adjust track height" feature proposed in this PR be configurable for a given track in config.json currently that is not part of this PR....
example of where per-track setting might be relevant a) situation like @nathanweeks refers to where admin might want it pre-configured b) situation where currently in this PR, clicking and dragging...
i think also the height calculation on the blocks might still have a race condition. from quickly moving around example screenshot below 
it could be worth experimenting with per track to see how it feels
close for now...will probably want to be revisited eventually
the weird thing about this error is that they are sometimes the same and sometimes not I made this small script ``` #!/bin/bash rm -rf b1 rm -rf b2 yarn...
We actually make a library that uses @mui/material and @mui/x-data-grid, so we try to be somewhat bundler agnostic, but in the example above we had a sample demo that used...