Not A Good Idea: Keeping all datasets of different scales within a single axis can cause issues when there’s wide gap between the values. For example in an auto scaled chart where the data values of the blue line are between 377 to 958, it can be hard to accurately read the lower values of the green line which are between 2 to 7.
Not A Good Idea: Placing the Legend on either sides of the chart when it contains long legend item labels can cause problems as shown below. The long text labels push the bars which scales the chart content to become smaller. In turn it causes the bottom labels to overlap each other making them hard to read.
Sparklines and Sparkbars are very small charts without the usual axes, tic lines or grids. This chart type is intended to show a trend in a clear and simple way in the text they’re part of.
Not A Good Idea: Displaying multiple datasets in rows is a problem as the first data set will cover the second dataset.
Not A Good Idea: Using unusually long bottom axis labels can pose a problem where they overlap each other completely, making the labels unreadable.
By default the popup labels (Dwell or Active Label) for both Bars and Lines are enabled when you hover over them in a Combo chart. However, you might have a particular requirement where you need to switch off the Active Labels for the Bars but need the Active Labels to remain for the Line data points.
Not A Good Idea: While using Analogous colors that sit next to each other look nice, colors used this way are not very functional. For example, it’s nearly impossible to identify a specific color of a label shown. If using a Legend, how do you easily identify which Label matches which slice?
Visual Mining product’s core rendering engines share the same Chart Definition Language (CDL) language. While CDL is a text based language, NetCharts Designer offers a user interface with wizards and menus to design and style the charts, removing the need to learn CDL.