ratt-ru / meqtrees

A library for implementing radio astronomical Measurement Equations
http://meqtrees.net
10 stars 2 forks source link

Result plotter does not properly update when switching active axes #741

Closed gijzelaerr closed 10 years ago

gijzelaerr commented 10 years ago
at 2009-10-02 16:34:17 Oleg Smirnov reported:

Result plotter does not properly update when switching active axes

gijzelaerr commented 10 years ago

Original comment thread migrated from bugzilla

at 2009-10-02 16:34:17 Oleg Smirnov replied:

When visualizing a result with >2 axes (i.e. time, freq, l, m), the Result Plotter gives us buttons along the bottom to pick the two "active" axes. When I use these buttons to go to switch to a different pair of axes (i.e. I select "time" and "l"), the initial image does not correspond to the data at all. If I then use the slider to move the current time-l slice along the freq axis back and forth, the correct image gets displayed and from that point on things work perfectly -- until I switch to another pair of axes, at which point another incorrect image is displayed.

at 2009-11-04 20:15:58 Tony Willis replied:

OK - I can now consistently replicate this problem with this case:

If we start with the l,m axes as fixed, then move the current time slider to the middle of the range somewhere, and then AGAIN select the l,m axes as fixed the colorbar range somehow gets way too big, causing the displayed data to all look 'light blue' as the actual data is somewhere near the bottom of the colorbar range.

I'll invesigate and fix.

at 2009-11-06 00:12:36 Tony Willis replied:

Should be OK now. I also fixed 'zoomer' problems that must have been there since day 1 when moving through a cube or switching from real/imag to amp/phase for complex data.

at 2009-11-06 00:15:32 Tony Willis replied:

NOTE: I also checked in all updates so that imaging of Color Bars and images should transit painlessly from PyQwt5.1 to Qwt5.2

at 2011-06-02 20:24:50 Tony Willis replied:

I'm marking this bug as resolved - I haven't heard any complaints for a long time.

Unfortunately I see that the QWT guy has now released a version 6 - I hope that the whole API hasn't changed as much as was the case with Qt going from 3 to 4 and Qwt going from 4 to 5 - grumble.