Bug: Prism 5 Windows doesn't display X axis correctly when the axis is labeled with row titles with many minor ticks.

Too many minor ticks

Prism 5 Windows (up to 5.04 and 5.0d) has problem when both of the following are true:

• The X axis of a Category graph is formatted to show row titles (the other choices are column titles, or row numbers).
• The number of minor ticks for text-scaled axis is set to be greater than the major ticks interval.

This situation is rare. If you want to show row titles on the X axis, generally you show each one. So there is little reason to ever change the default:  interval of 1 (show every row label), with no minor intervals.

If your data table has lots of rows, it can make sense to set the major interval a higher number. For example, set the interval to 3 to show every third label. In this case, you'll probably want to set the minor intervals to 3 to put a minor tick under each category. That works fine. Problems only would occur in this case if you made the minor interval greater than 3, which would  show more minor ticks than there are rows of data.  Category graphs with more minor ticks than rows of data are not very attractive or informative, so graphs are rarely made that way,  which explains why we didn't discover this problem for so long. Of course, we'll fix it.

Note that showing row numbers is fine, with any number of minor ticks. The problem only occurs when you choose to label the X axis with row titles, and choose to have more minor ticks than there are rows of data.

The problem only occurs with Prism Windows. Trying to view a graph with more minor ticks that row labels in the table can cause Prism to crash.  If this happens to you, send us the file and we can fix it.

Row titles aren't shown at all

This is a new bug in 5.04. If you create an XY data table, and enter both row titles and X values, Prism will not let you label the X axis with the row titles. That choice will appear in the Format Axes dialog, but it will be ignored. The X values will show instead. There is an easy workaround: Delete all the X values. If there are no X values, then Prism will use the row titles.