On Wed, Aug 12, 2009 at 12:36 PM, Chris Foster<
chris42f@...> wrote:
> Regarding the interface, how about making the channelnames into an array:
>
> Display ... "string channelnames" ["X" "Y" "Z"]
>
> The array length would be known by what type of AOV you're displaying.
After discussing this briefly at the meeting, I've come to think that my
solution above isn't any good, mainly because there's no guarentee that the
channel names array will be passed portably through the interface and into
DspyImageOpen.
At first I thought it would be a really odd implementation to not pass through
the array correctly, but there's probably various reasons why the renderer
might want to cache the RI calls somehow and recall them later. The most
obvious example would be InlineArchive - in that case, the renderer really
needs to know the length of the channelnames array so that it can copy and
save it somewhere.
I think this leaves us with what you had before (using parameter name
numbering), or the following, which I think is a little nicer:
Display "string channelnames[3]" ["X" "Y" "Z"]
If we use this I think it's fairly clear that it will be correctly handled by
other renderers, not just aqsis.
The interface drawback is that the user has always to write an inline
declaration with the correct array size, but I think this is less of a burden
than creating several independent numbered channel names.
~Chris.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.
http://p.sf.net/sfu/bobj-july_______________________________________________
Aqsis-development mailing list
Aqsis-development@...
https://lists.sourceforge.net/lists/listinfo/aqsis-development
