jalview

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
JAL-4071 colour rows according to simple/graduated feature colour, beginning of support for complement features

    • -2
    • +2
    /examples/groovy/featuresCounter.groovy
    • -5
    • +12
    /src/jalview/workers/ColumnCounterSetWorker.java
    • -10
    • +12
    /src/jalview/workers/FeatureSetCounterI.java
JAL-4071 first working prototype

    • -5
    • +27
    /src/jalview/api/FeatureRenderer.java
    • -24
    • +36
    /src/jalview/gui/AlignmentPanel.java
    • -4
    • +24
    /src/jalview/workers/ColumnCounterSetWorker.java
    • -0
    • +183
    /src/jalview/workers/VisibleFeaturesAnnotationTracks.java
JAL-4071 boring GUI bits - add togglable menu item for show/hide sequence feature counts and viewModel/viewStyleI methods

    • -7
    • +14
    /src/jalview/api/AlignViewportI.java
    • -11
    • +11
    /src/jalview/gui/AlignViewport.java
    • -12
    • +32
    /src/jalview/jbgui/GAlignFrame.java
JAL-4065 release notes for JAL-4014 and JAL-4063 in 2.11.2.5

JAL-4065 - new release notes featuring JAL-3612 fix

    • -0
    • +12
    /help/markdown/releases/release-2_11_2_5.md
Merge branch 'bug/JAL-3612_overviewFeatureOrdering' into develop

JAL-4014 JAL-4063 Added gecos colourScheme names (INFO message) and fixed Clustal colourScheme name

    • -1
    • +5
    /resources/lang/Messages_es.properties
JAL-4046 release on 9th August 2022

JAL-4046 JAL-3993 imports reformatting

JAL-4046 JAL-3993 patch for 2.11.2.4 release

JAL-4046 release notes for JAL-3991

Merge branch 'task/JAL-3991_check_actual_JAVA_VERSION_against_build_properties_in_application_startup' into develop

    • -0
    • +4
    /resources/lang/Messages_es.properties
JAL-4046 release notes for JAL-4014 - gecos colourschemes

Merge branch 'improvement/JAL-4014_gecos_colour_schemes' into develop

JAL-4056 documented in release notes for JAL-4043

Merge branch 'patch/JAL-4036_uniprot_fts_legacy_endpoint' into develop

JAL-4043 what’s new, updated help images and release notes for JAL-4034 (3d beacons button)

    • binary
    /help/help/html/features/3dbeacons_button.png
    • binary
    /help/help/html/features/schooser_main.png
    • -0
    • +2
    /help/markdown/whatsnew/whatsnew-2_11_2_4.md
JAL-4034 show the loading spinner when switching between tabs

    • -0
    • +2
    /src/jalview/gui/StructureChooser.java
Merge branch 'features/JAL-4034_improve_3dbeacons_button_and_ux' into develop

JAL-4056 fixed tl;dr section of doc/building.md

JAL-4036 Fixed the virus_host_id query field

    • -1
    • +1
    /resources/fts/uniprot_data_columns-2022.txt
JAL-4036 Added text to help about different number and date range acceptable formats

JAL-4036 updated help about new UniProt API

JAL-4036 moved a comment block

JAL-4034 button looks better also on other OSes with the 0 vertical insets

    • -7
    • +4
    /src/jalview/jbgui/GStructureChooser.java
JAL-4034 add round corners to 3DB confirmation button with icon on a mac

    • -4
    • +14
    /src/jalview/jbgui/GStructureChooser.java
JAL-4036 Changes made from code review CR-JAL-265

I've now put in a warn with the e.getMessage(), but I've left in a debug with the full stacktrace. This catch block is a little odd in that it's used as programmatic flow for non 200 HTTP responses...

I've now put in a warn with the e.getMessage(), but I've left in a debug with the full stacktrace.
This catch block is a little odd in that it's used as programmatic flow for non 200 HTTP responses. I notice that the new API server is sending back a 400 for bad input (including for non-existent query fields and wrong types for non-string query fields), which is invoking the warning triangle which puts the HTTP error message into the tooltip so this block is now getting more use!

The reason for wanting a full stacktrace in debug mode is that both the API and the changed client are new, so any errors in the next few months will be more quickly diagnosed if we can allow the user to easily obtain a stacktrace of the exception.

after trying it out I think the old behaviour is better, unless 1) there's a really clear message in the UI explaining that now the field has changed, the search needs to be executed again 2) a con...

after trying it out I think the old behaviour is better, unless 1) there's a really clear message in the UI explaining that now the field has changed, the search needs to be executed again 2) a convenient [search] button is shown so one doesn't have to click into the query field and press enter to trigger the search again.