limitations in odgibasevectorizer::draw(const odgidrawable*)
limitations in odgibasevectorizer::draw(const odgidrawable*)
given that odgibasevectorizer has all the contexts etc correctly set up, is odgibasevectorizer::draw(const odgidrawable*) a totally selfcontained function which will completely render a oddbentity?
i would like to controle the generation of geometry myself instead of sending it off to pview->update(). is there a lot of magic going on inside odgsview::update() that i cannot emulate in my own code?
-rune jorgensen
www.dds.no
hi,
yes, odgibasevectorizer::draw(const odgidrawable*) is a totally self-contained function on odgibasevectorizer class level. but it's not guaranteed for odgibasevectorizer derived classes.
our implementations of odgsview::update() perform some internal per-view initializations and call odgigeometry::draw() for all drawables added via odgsview::add().
odgsdevice::update() of object returned by oddbgsmanager::setuppaperviews() controls lay-out of views in paper space related on overall viewport's view.