This resolves the reported issue. I've tested the data that was included in that issue (FYI the example was mapped to GRCh37) and these modifications now render this data more appropriately.
I wasn't sure how to show the large scale N skip in the padded alignment so have inserted '~NNNN~' in the query, target and match text, where 'NNNN' is the number of bases skipped (this is going to look odd if split across lines). Perhaps '~~' would be less of an issue for formating, but in turn less informative.
This resolves the reported issue. I've tested the data that was included in that issue (FYI the example was mapped to GRCh37) and these modifications now render this data more appropriately.
I wasn't sure how to show the large scale N skip in the padded alignment so have inserted '~NNNN~' in the query, target and match text, where 'NNNN' is the number of bases skipped (this is going to look odd if split across lines). Perhaps '~~' would be less of an issue for formating, but in turn less informative.
Over to someone else to make the final decisions...