Opened 8 years ago
Closed 8 years ago
#12338 closed defect (fixed)
dojox.charting.Theme() forces defaultMarkers when custom Markers are defined
| Reported by: | Karl Tiedt | Owned by: | Eugene Lazutkin |
|---|---|---|---|
| Priority: | high | Milestone: | 1.6 |
| Component: | Charting | Version: | 1.6.0rc1 |
| Keywords: | dojox.charting.Theme themes charting defaultMarkers setMarkers | Cc: | |
| Blocked By: | Blocking: |
Description
If you call theme.setMarkers() it blows away the defaultMarkers array for that theme (as expected) However, when you call chart.setTheme(myThemeWithoutDefaultMarkers) it clones the custom theme which invokes the constructor in Theme() which dojo.delegates() the defaultMarkers BACK into the theme... (not expected)
Change History (2)
comment:1 Changed 8 years ago by
| Milestone: | tbd → 1.6 |
|---|
comment:2 Changed 8 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
(In [23876]) charting: don't blow away custom markers, thx tk!, !strict, fixes #12338.