X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2FwhatsNew.html;fp=help%2Fhtml%2FwhatsNew.html;h=1c2088579ed5e6c1ff6426efcdcc65b30092e996;hb=883124d6710f98993ea7cdd3dbb311106999d559;hp=e8b9c968e681dfb9370e5db239c6bd73833930d8;hpb=9488c71b93efc8b28aada795c80c2a9ca3945844;p=jalview.git diff --git a/help/html/whatsNew.html b/help/html/whatsNew.html index e8b9c96..1c20885 100755 --- a/help/html/whatsNew.html +++ b/help/html/whatsNew.html @@ -40,13 +40,12 @@
  • Select highlighted region
    Press 'B' or use the new menu option in the alignment window's Select menu to mark columns containing highlighted regions generated from - structure selections, mouse-overs, or resulting from a - Find operation.
  • + structure selections, mouse-overs, or resulting from a Find + operation.
  • New custom link mechanism for opening URLs for database cross references.
    If you have customised URL links in your Jalview preferences, then you may already have seen - the Update your links - warning dialog.
  • + the warning dialog (see below).
  • New command line export option for BioJS MSAviewer
    A number of small bugs with the HTML export functions from the Jalview desktop were also fixed.
  • @@ -55,7 +54,25 @@ is no longer considered a non-hydrophobic residue in the protein conservation calculation, and minor bugs addressed in PID and consensus colouring. +
  • Correct display of disulphide bond + features
    In linked structure views, Jalview would + highlight all residues between in addition to the two linked + cysteines. The 'select columns by feature' function in the feature + settings would also select all intermediate columns. +

    + Warning dialog about updating + your configured URL links
    In the desktop prior to Jalview + 2.10.1, the only way to configure custom links for a particular + database cross-reference for a sequence was to give it a name that exactly + matched the database source, and a regular expression for filtering + out any spurious matches generated when the custom linked was tested + against the Sequence's ID string. Since the introduction of the + $DB_ACCESSION$ token, however, $SEQUENCE_ID$ will not be used for + database cross-reference accession strings, and if you have custom + links configured, Jalview will raise a warning message so let you + know that you may need to update your links to use $DB_ACCESSION$. +