Task #9138 (closed)
Opened 12 years ago
Closed 12 years ago
Bug: Web/SplitView
| Reported by: | saloynton | Owned by: | wmoore |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | Web | Version: | n.a. |
| Keywords: | phase1, testing | Cc: | saloynton |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Tricky one-- in split view, single image. then change rendering settings in full view, save, then go back to single image. max projection does not obey new rendering settings.
- Windows 7(64 bit)
- OMERO.web 4.3.3-2767-36f59d2-ice33-b74.
- Check browser with Jason
Change History (5)
comment:1 Changed 12 years ago by wmoore
- Milestone changed from OMERO-Beta4.4 to OMERO-Beta4.4.1
comment:2 Changed 12 years ago by wmoore
- Cc saloynton added; web-team@… ux@… removed
- Sprint set to 2012-07-31 (1)
comment:3 Changed 12 years ago by wmoore
- Status changed from new to accepted
comment:4 Changed 12 years ago by wmoore
- Milestone changed from OMERO-4.4.2 to Unscheduled
- Sprint 2012-07-31 (1) deleted
Had another look at this:
Upon saving E.g. new colours in image viewer, if you already had the split-view figure open, we have no way of knowing the colours have changed - so the figure header form remains the same. Even when we update the figure, rendered image panels are cached by the browser. We'd have to know to ask for non-cached: E.g. url?_12343233434242311 or something.
Not trivial fixes - and this plugin is still not turned on in the released webclient, so pushing for now...
comment:5 Changed 12 years ago by wmoore
- Resolution set to wontfix
- Status changed from accepted to closed
Since this is an edge-case bug in a feature-set that isn't part of the released webclient, and will require a few code changes etc, I'm not going to fix this anytime soon. Can re-open if priority changes.
I guess the split-view plugin should not 'remember' colour settings and channel levels, but should get these from the server each time.
However, since the plugin will not be part of the release, this will not be fixed for 4.4