yang686526

design for interruption, resume, and random seek
design for interruption, resume, and random seek
hello,
for our application we need to be able to render an autocad file. (of course.) but the catch is that in the middle of rendering, the app might be paused. and then told to resume from where it paused.
another catch is that after running through all the entities of an autocad file, our app may ask about previously rendered entities. for example, the app may ask, what was that information about the 7th entity you told me about before? okay tell me about the 21st entity again? oh and the 3rd entity, what was that about?
can you suggest some general ways we might best go about implementing this with dwgdirect? i have some ideas but figured you guys would have a better feel for how best to implement interruption, random seek, and resume.
thanks!
alrite, that was apparently too convoluted a post. let's try again;-)
i did do a search, apparently i'm not the only one wanting to pause a vectorization operation! i see that no responses were given to those questions either.
so, let's say i've set everything up and called device::update(). in vectorizedevice::draw(), i see that i can at that point see if i need to pause. at that point, i know i can call abort(), but is there a way to remember where i was so that on a subsequent update() call, the vectorization picks up where it left off?
by overriding odgicommondraw::regenabort() (callback) and returning true from it you can terminate the process of vectorization. but you can't resume it.
sergey slezkin