yang686526

vectorizing paperspace layouts
vectorizing paperspace layouts
hello,
i磎 looking for a useful hint to solve my problem after a week of ineffective attempts.
the task is to import and display paperspace layouts in a cad system - until yesterday, the content of viewport entities was missing.
with the discovery of the function
"oddbgsmanager::setuplayoutviews(oddbobjectid layoutid, odgsdevice* pdevice, odgicontextfordbdatabase* pgictx)"
and using the vectorization framework of od,
i implemented a code, which seems to perform the task.
i would be happy, if there wasn磘 a hitch:
the first paperspace layout, which is to be vectorized, is displayed as only two lines.
following paperspaces are completely vectorized.
the paperspaces are vectorized in order of their appearance in the blocktable section.
for example: when importing a drawing, that contains three paperspace layouts, the function "initpsentity" [below] is called triply, once for each paperspace layout.
is it, that i fail to do some initialisation or maybe the fault occurs because i don磘 vectorize model layout?
i append my code, please take attention to the comments, which should explain the problem.
int dxfdbstrakon::initpsentity()
{
dxfdbstrakon* pdxfdb = getdxfdbstrakonobj();
odgsinitialize();
odgicontextfordbdatabaseptr pdwgcontext = odgicontextfordbdatabase::createobject();
file* output=fopen("viewportvectorization.dat","w");
odgsdeviceptr pdevice = viewportvectorization::createobject(output,
viewportvectorization::k3ddevice);
pdwgcontext->setdatabase(pdxfdb->m_pdb);
// m_pactivelayoutid is a member of class dxfdbstrakon, which controls the import.
// this member is set by searching the blocktable section for blocktablerecords with
// a "layout" identifier.
// i assured, that m_pactivelayoutid is always a paperspace id!
pdevice = oddbgsmanager::setuplayoutviews(m_pactivelayoutid, pdevice, pdwgcontext);
// called for the first time, this query returns always one, which is incorrect!
// called later, the query returns the number of the viewports in the layout plus one.
int numviews = pdevice->numviews();
odgsdcrect screenrect(odgsdcpoint(0, 0), odgsdcpoint(100, 100));
pdevice->onsize(screenrect);
pdevice->update();
odgsuninitialize();
return 0;
}
the overridden "odgsbasevectorizationview::update()" function looks mostly like the exsimpleview
example:
void viewportvecview::update()
{
device()->setdrawcontext(drawcontext());
// first viewport is overallviewport
odgsviewptr poveralview = device()->viewat(0);
if (!poveralview.isnull())
{
odgematrix3d xmodel2paperspace =
(poveralview->screenmatrix() * poveralview->projectionmatrix()).inverse()
* eyetoscreenmatrix();
seteyetooutputtransform(xmodel2paperspace);
}
else
{
return;
}
// perform viewport clipping in eye coordinates:
m_eyeclip.m_bclippingfront = isfrontclipped();
m_eyeclip.m_bclippingback = isbackclipped();
m_eyeclip.m_dfrontclipz = frontclip();
m_eyeclip.m_dbackclipz = backclip();
m_eyeclip.m_vnormal = viewdir();
m_eyeclip.m_ptpoint = target();
m_eyeclip.m_points.clear();
double width=fieldwidth();
double height=fieldheight();
odgevector2d halfdiagonal(fieldwidth() / 2.0, fieldheight() / 2.0);
if(m_nrccounts.size() == 1) // polypolygons aren't supported yet
{
// polygonal clipping
int i;
for(i = 0; i < m_nrccounts[0]; i ++)
{
odgepoint3d screenpt(m_nrcpoints[i].x, m_nrcpoints[i].y, 0.0);
// screenpt.transformby(screen2eye);
m_eyeclip.m_points.append(odgepoint2d(screenpt.x, screenpt.y));
}
}
else
{
// rectangular clipping
m_eyeclip.m_points.append(odgepoint2d::korigin - halfdiagonal);
m_eyeclip.m_points.append(odgepoint2d::korigin + halfdiagonal);
}
m_eyeclip.m_xtoclipspace = getworldtoeyetransform();
pushclipboundary(&m_eyeclip);
odgsbasevectorizeview::update();
popclipboundary();
}
our dwf export is a sample illustrating vectorizing multiple layouts and writing them to dwf file.
sergey slezkin
thank you very much for your detailed and assistant answer to my question...