Opened 10 years ago

Closed 10 years ago

#11356 closed enhancement (fixed)

Secondary/indirect charting events.

Reported by: Eugene Lazutkin Owned by: Eugene Lazutkin
Priority: high Milestone: 1.5
Component: Charting Version: 1.5.0b2
Keywords: Cc:
Blocked By: Blocking:

Description

In some cases event subscribers need to know that an event has happen with a neighboring plot, so they can modify their visuals, or update UI. We need to add a secondary/indirect notifications to subscribers.

Change History (6)

comment:1 Changed 10 years ago by Eugene Lazutkin

(In [22352]) charting: event normalization and added "indirect" events, thx vmware!, !strict, refs #11356.

comment:2 Changed 10 years ago by Eugene Lazutkin

Status: new → assigned

See if it makes sense to move all event-related functionality from Base to Element. It'll reduce the duplication we have now --- the Pie plot is derived directly from the Element, and has to reimplement all event-related methods.

comment:3 Changed 10 years ago by Eugene Lazutkin

(In [22372]) charting: refactored event support + added a support for programmatic events, thx vmware!, !strict, refs #11374, refs #11356.

comment:4 Changed 10 years ago by Eugene Lazutkin

(In [22375]) charting: eliminating potential memory leaks in programmatic events, thx vmware!, !strict, refs #11356, refs #11374, refs #10827.

comment:5 Changed 10 years ago by Eugene Lazutkin

(In [22377]) charting: the test case for recent event enhancements, thx vmware!, !strict, refs #11356, refs #11374.

comment:6 Changed 10 years ago by Eugene Lazutkin

Resolution: → fixed
Status: assigned → closed
Note: See TracTickets for help on using tickets.