Task #5553 (closed)
BUG: Web Line-plot not all visible if zoom over 100%
Reported by: | ajpatterson | Owned by: | cneves |
---|---|---|---|
Priority: | minor | Milestone: | Usability Backlog |
Component: | Web | Version: | n.a. |
Keywords: | n.a. | Cc: | ux@…, atarkowska, wmoore, cneves, jburel |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description
If you zoom in so that the image is larger than the window so you have scroll bars, move to the middle of the image. Turn on a line plot vertically, Pick a point, most of the line plot is drawn off screen.
This seams odd, I would assume the plot to be locked so the edge of my window is 0, so I can see the full height of my plot.
Might not be a bug but it was not what I expected to happen.
Change History (11)
comment:1 Changed 13 years ago by atarkowska
- Owner changed from atarkowska to cneves-x
comment:2 Changed 13 years ago by atarkowska
- Cc atarkowska wmoore added
comment:3 Changed 13 years ago by jburel
- Sprint changed from 2011-06-02 (13) to 2011-06-16 (14)
comment:4 Changed 13 years ago by cneves
- Milestone changed from OMERO-Beta4.3 to OMERO-Beta4.3.1
- Owner changed from cneves-x to ajpatterson
- Sprint 2011-06-16 (14) deleted
If I understand your report correctly, you are describing the expected behaviour. The line plot scale is arbitrary and max intensity is at top (or right, in this case) of the image and the intersecting point on line plot is the respective X or Y position. The line plot viewport is basically the image.
There are alternatives to this, like keeping the lineplot value axis contained on the viewport, which in the case you report would mean leftmost of viewport would be 0, rightmost would be max intensity regardless of image zoom and horizontal position. The position axis (vertical) would be scaled and move with the image (somewhat complex to achieve).
Another alternative would be a separate line plot widget, but I don't think we can guarantee we'll have the screen real estate for that.
All in all this is not a bug per se, so while we may decide to change this for a future release, I'm taking it off of OMERO4.3, as I don't think we're doing new features anymore.
comment:5 Changed 13 years ago by jburel
- Cc cneves-x jburel added
comment:6 Changed 13 years ago by jmoore
- Owner changed from ajpatterson to cneves-x
Re-assigning to Carlos for handling post-release. Tickets will be moved to 4.3.1 (or Unscheduled) when 4.3 is closed.
comment:7 Changed 13 years ago by atarkowska
- Milestone changed from OMERO-Beta4.3.1 to OMERO-Beta4.3.2
comment:8 Changed 13 years ago by atarkowska
- Milestone changed from OMERO-Beta4.3.2 to Unscheduled
comment:9 Changed 13 years ago by jburel
- Milestone changed from Unscheduled to Usability Backlog
comment:10 Changed 12 years ago by cneves
- Resolution set to invalid
- Status changed from new to closed
This is expected behaviour, but can obviously be improved. Closing it as no one else ever mentioned this being a problem.
comment:11 Changed 12 years ago by jmoore
- Cc ux@… added
Moved from sprint 2011-06-02 (13)