Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #8758 (closed)

Opened 12 years ago

Closed 11 years ago

Bug: Inconsistent behaviour of brightness/contrast adjustment sliders

Reported by: rleigh Owned by: wmoore
Priority: major Milestone: Usability Backlog
Component: Web Version: 4.4.8
Keywords: n.a. Cc: ux@…
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

When adjusting the channel min/max values after choosing "edit channels", the min/max values are only settable within the min/max intensity range of the pixel values within the image (plane/stack/series?--unsure what the constraints are). It is not possible to set values within the actual dynamic range of the pixel values. This is useful if one wishes to normalise the values between a set of images, or use values outside this range to e.g. reduce the visible background. However.... it's possible to manually specify the numbers in the entry boxes, and these /can/ be set outside the range, but if the sliders are touched they are immediately clipped to within the range again. This behaviour is somewhat confusing. Maybe allow use of the full range, and have an "auto" button which sets it to the min/max intensity or a certain percentile within the range.

Attachments (2)

web-channel-range-sliders.png (45.2 KB) - added by rleigh 12 years ago.
Range sliders
web-channel-sliders-clipping.png (35.5 KB) - added by rleigh 12 years ago.
Range sliders clipping

Download all attachments as: .zip

Change History (8)

Changed 12 years ago by rleigh

Range sliders

Changed 12 years ago by rleigh

Range sliders clipping

comment:1 Changed 12 years ago by atarkowska

  • Milestone changed from OMERO-Beta4.4 to Usability Backlog
  • Owner changed from web-team@… to sloynton

comment:2 Changed 12 years ago by saloynton

This has also been recored in the usability tab in the phase 1 testing gdoc - the ticket needs to be revisited post 4.4. The priority has also been downgraded.

comment:3 Changed 12 years ago by saloynton

  • Cc ux@… added
  • Priority changed from critical to major

comment:4 Changed 11 years ago by jburel

  • Owner changed from sloynton to wmoore

comment:5 Changed 11 years ago by wmoore

From JM: slider: 0-255. The max pixels type range is 0-255
User can enter negative values. Does not seem right
From https://docs.google.com/spreadsheet/ccc?key=0ArfUkRuStsCEdGY0Mk9vSWlkaE9iRlNHODkzdkMwMVE&pli=1#gid=14

comment:6 Changed 11 years ago by wmoore

  • Resolution set to fixed
  • Status changed from new to closed
  • Version set to 4.4.8
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.68604 sec.)

We're Hiring!