Re: Problem with new binary input code

[Daniel J S. <dan...@ie...>]

Ethan Merritt wrote:

>On Sunday 12 September 2004 09:24 am, Ethan Merritt wrote:
>  
>
>>In datafile.c there is an array
>>
>> df_bin_default_columns default_style_cols[LAST_PLOT_STYLE + 1] = {
>>    {1, 1}, /* LINES */
>>    {1, 1}, /* POINTSTYLE */
>>    [... and so on]
>>    
>>
>
>And another question occurs to me.
>How does this work at all for plot styles which apply both to
>2D and 3D plot styles?  I may have missed it, but I couldn't
>find a line of code that adjusts the expected number of 
>columns to be 1 greater in 3D mode.
>

It's in there somewhere...

        /* If there aren't generated coordinates, then add the
         * amount of columns that would be generated.
         */
        no_cols += default_style_cols[plot_style_index].dimen_in_2d;
        if (df_plot_mode == MODE_SPLOT)
            no_cols++;

The above may be it.  In any case, I'm sure I addressed this.  I guess 
my approach to things is that all styles should be allowed to be 
extended to 3D plots, as far as generating the data, that is.  Whether 
further down the line the plotting code can make sense of extending the 
plot style to 3D is another matter...  I also wonder if the "properties 
of plotting styles", default using specs and behavior, extending data to 
3D, better integration of plot2d.c/plot3d.c are all part of the grand 
scheme...  That is sort of why I wrote the image routine to allow 
passing in MODE_SPLOT or MODE_PLOT.  It can then be used in both plot2D 
and plot3D.c, for what that is worth.  One could take the same approach 
with other styles (e.g., bar graphs in 3D... although 3D bar graphs may 
be a faux pas of graphing, i.e., simply a wow factor and/or means to 
distort results).

Dan