Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0.2
    • Component/s: Web Interface
    • Labels:
      None

      Description

      Stuart: Range setting sliders don't behave well for the case of specifying a small
      part of the range from min to max. That is if a variable has a range from
      0 to 1, but what we're interested in is looking in detail at 0.0001 steps
      from 0.0012 to 0.0022, then it is very difficult to set 0.0012 and 0.0022.

      LD: In think you are referring here at the ability to change this value from keyboard arrows
      Noted, but this is low priority.

      SK: The arrows thing is an issue too, but here I'm referring to the ability to
      set a range significantly different to the complete one. To see this, as an arbitrary example, try and set the parameter 'a' for FitzHughNagumo to have a range from 1.0001 to 1.0002 (the specific example is contrived, but the basic specificity is required). Marmaduke's comment about having text field for high and low of the range would be one solution.

      LD2: Currently the min and max values for the range seems to work with 2 decimals only.
      We should be able to extend this (support a variable number of decimals, based on default ranges, or on a traited field).
      I would more than gladly take Marmaduke's suggestion, but the option with having text fields for high and low is not really an option, as when we had the requirements specified for a range, the UI control was one of them. I specifically remember there was a drawing of it. :-|

        Attachments

          Activity

            People

            • Assignee:
              bogdan.neacsa Bogdan Neacsa
              Reporter:
              stuart.knock Stuart Knock
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 day
                1d
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day
                1d