Free cookie consent management tool by TermsFeed Policy Generator

Opened 8 years ago

Closed 8 years ago

#2662 closed enhancement (done)

Show Y-Value in Target Response Gradients

Reported by: pfleck Owned by: mkommend
Priority: medium Milestone: HeuristicLab 3.3.15
Component: Problems.DataAnalysis.Views Version: 3.3.14
Keywords: Cc:

Description

Similar to the current x-value, show the corresponding y-value when the cursor is changed.

Change History (11)

comment:1 Changed 8 years ago by pfleck

  • Status changed from new to accepted

comment:2 Changed 8 years ago by pfleck

r14267

  • Show the current y value on the y-axis label.
  • Changed format of the x- and y-value to fixed significant digits ("G") instead of fixed decimal digits ("N").

comment:3 Changed 8 years ago by pfleck

  • Owner changed from pfleck to mkommend
  • Status changed from accepted to reviewing

comment:4 Changed 8 years ago by mkommend

  • Owner changed from mkommend to pfleck
  • Status changed from reviewing to assigned

Small error wrt to event registration of the shared variables. Use Register- DeregisterContentEvents for event registration.

comment:5 Changed 8 years ago by pfleck

  • Status changed from assigned to accepted

comment:6 follow-up: Changed 8 years ago by pfleck

r14307 Fixed the event deregistration.

In this case I cannot use the Register- and DeregisterContentEvent methods. The event I want to register to is created during OnContentChanged and RegisterContentEvents is called before OnContentChanged (see line 48-51 in ContentView.cs). Therefore it would be null during RegisterContentEvents.

I was surprised because I suspected that OnContentChanged would be called between DeregisterContentEvents and RegisterContentEvents, not afterwards.

comment:7 Changed 8 years ago by pfleck

  • Owner changed from pfleck to mkommend
  • Status changed from accepted to reviewing

comment:8 Changed 8 years ago by mkommend

Reviewed r14307.

comment:9 in reply to: ↑ 6 Changed 8 years ago by mkommend

Replying to pfleck:

I was surprised because I suspected that OnContentChanged would be called between DeregisterContentEvents and RegisterContentEvents, not afterwards.

The reason for this is that events cannnot get lost that occur while creating and updating the view in the OnContentChangedMethod. Hence, the events have to be registered before OnContentChanged is called.

comment:10 Changed 8 years ago by mkommend

  • Status changed from reviewing to readytorelease

comment:11 Changed 8 years ago by gkronber

  • Resolution set to done
  • Status changed from readytorelease to closed

r14570: merged r14267 and r14307 from trunk to stable

Note: See TracTickets for help on using tickets.