Hi Stefan,
Thanks. In a similar vein, I notice that the data in FrameData
is a Matrix4f, a Vector3f, and a bool. The first two classes have
data as well. The way eqlPly transfers the data from master to
the nodes/pipes implies that there cannot be pointers in the data
at any level, only value data. For example, if Matrix4f had a pointer
to 16 elements, the code would fail. I believe it is very important
to put this in the documentation somewhere.
Gordon
Quoting Stefan Eilemann <[EMAIL PROTECTED]>:
>
> On 15. Jan 2008, at 22:18, Gordon_Erlebacher wrote:
>
>> Hi,
>>
>> Here is a simple question:
>
> Nice. :)
>
>>
>>
>> Why is FrameData in eqPly not subclassed from eq::FrameData ? Would
>> that not make more
>> sense? What are the rules regarding what is subclassed from what in
>> order to reduce the chance
>> of error?
>
>
> Naming clash. The eq::FrameData is the holder for images (pixel data)
> during
> image compositing. The eqPly::FrameData is the per-config-frame data
> holding
> (rendering) frame-specific data, e.g., the global camera. Thus the two
> FrameData
> are fundamentally different animal.
>
> Maybe I should rename eq::FrameData.
>
>
> Cheers,
>
> Stefan.
>
>
> _______________________________________________
> eq-dev mailing list
> [email protected]
> https://in-zueri.ch/cgi-bin/mailman/listinfo/eq-dev
> http://www.equalizergraphics.com
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
Gordon Erlebacher
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
eq-dev mailing list
[email protected]
https://in-zueri.ch/cgi-bin/mailman/listinfo/eq-dev
http://www.equalizergraphics.com
