Hi Fatih, Welcome to the list!
On 5. Jan 2009, at 18:13, Fatih Erol wrote: > Are there any limitations for the 'frame ID' we assign to the > frames? Does > the server or client library have an internal mechanism to alter and > differentiate it, or should we give the frame id with the > config->startFrame() function parameter and increment it > appropriately? Is > this frame ID we assign only for the client developer's benefit, and > does > the equalizer tag the frames internally for its own use? The frame id is application-specific. You can think of it as the 'void* userdata' commonly used in C API's. It is passed (but not altered) by Equalizer from Config::startFrame to all frameFoo() task methods. There is also a frame number generated by Equalizer, which gets passed into some frameFoo() task methods, e.g., startFrame(). > What will be the effect of calling config->startFrame(0) always in a > 2D > decomposition config? In DPLEX config? None, other that your frameFoo() callbacks might expect something else than 0. The typical use case is explained in Section 5.3. Distributed Objects of the PG, esp. 5.3.5. HTH, Stefan. _______________________________________________ eq-dev mailing list [email protected] http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
