X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2FwhatsNew.html;h=d1d141d30b133f0a400e7fb369ebe9cce029c4d5;hb=47fd498a6fe7d2e3350a9e87c526bf1e59d00be5;hp=3f402dc7dc0028fdc6b5aa125c522667c202fc11;hpb=dfabc2facf04bc805f0b6001b94de3c62b3049b0;p=jalview.git diff --git a/help/html/whatsNew.html b/help/html/whatsNew.html index 3f402dc..d1d141d 100755 --- a/help/html/whatsNew.html +++ b/help/html/whatsNew.html @@ -1,58 +1,78 @@ + * You should have received a copy of the GNU General Public License + * along with Jalview. If not, see . + * The Jalview Authors are detailed in the 'AUTHORS' file. + --> What's new ? -

What's new ?

-

The Jalview 2.6.1 release fixes a number of minor bugs affecting -Jalview operation, including issues affecting the import and export of -PIR files and working with multiple multiple structure superpositions. -For full details see the Jalview -2.6.1 release history.

-

Highlights in Jalview Version 2.6

- - -

Issues Resolved (a select list - see release -history for details)

- -

See the Release History page for -details of all new features and resolved issues.

+

+ 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$. +