In an upcoming release, we are retooling the XML reading and the performance
will not be an issue. Folks will just have to bear with us until then.
"Rodney McManamy - CADzation" wrote in message
news:40d22f76$1_2@newsprd01...
> Jeffrey,
>
> Any chance of getting an option to where it doesn't do that? Sure it
would
> take longer when you select an object to find the properties but I've
heard
> quite a bit of interest from the GIS side of things in DWF and I imagine
one
> of the main reasons is for the properties that can be attached.
>
> Or if it can only build up for the objects that are visible that would
> normallly cut it in at least 1/4 if not more since normally they would
have
> to be zoomed in to select something.
>
> --
> Rodney McManamy
> President
> CADzation
> -------------------------
> rmcmanamy@cadzation.com
> -------------------------
> 518 South Route 31 Suite 200
> McHenry, IL 60050
> www.cadzation.com
> Providing Industrial Strength
> PDF & DWF Solutions to the
> Global CAD Marketplace.
>
> "Jeffrey Klug (Autodesk, Inc.)"
wrote
> in message news:40d2272b$1_1@newsprd01...
> > The first time you mash the select tool, the viewer has to materialize
an
> > XML file containing all of the object properties. Depending on how you
> > publish it, you could end up with 20Mb of XML data (per page!), which is
> > what is taking so long to read in. Like John mentioned earlier, try to
> > avoid selecting all of the property sets when publishing object
properties
> > out of ADT.
> >
> >
> > "Rodney McManamy - CADzation" wrote in message
> > news:40d207e0_3@newsprd01...
> > > You're not kidding on that one. Ouch. We're investing pretty heavily
> in
> > > supporting the DWF and I guess I've never once tried to select an item
> in
> > a
> > > file that large to see what it would do. That's worse than the image
> > > display.
> > >
> > > --
> > > Rodney McManamy
> > > President
> > > CADzation
> > > -------------------------
> > > rmcmanamy@cadzation.com
> > > -------------------------
> > > 518 South Route 31 Suite 200
> > > McHenry, IL 60050
> > > www.cadzation.com
> > > Providing Industrial Strength
> > > PDF & DWF Solutions to the
> > > Global CAD Marketplace.
> > >
> > > "Murph" wrote in message
> > > news:40d1f851_3@newsprd01...
> > > > They both opened fairly quick for me also, BUT selecting an object
is
> > > > slowwwwwwwwwwww.
> > > > I ended up cancelling out with the big X.
> > > >
> > > > Murph
> > > >
> > > > "Rodney McManamy - CADzation" wrote in
> message
> > > > news:40d1f4c1_1@newsprd01...
> > > > > I just tested both your samples on mine and it takes about 3
seconds
> > > each
> > > > to
> > > > > open in Composer. I have build version 1.0.0.2161
> > > > >
> > > > > HP 2.4 ghz Pentium 4 Laptop
> > > > > 512 MB memory
> > > > >
> > > > > And the options in Composer are set to the defaults.
> > > > >
> > > > > --
> > > > > Rodney McManamy
> > > > > President
> > > > > CADzation
> > > > > -------------------------
> > > > > rmcmanamy@cadzation.com
> > > > > -------------------------
> > > > > 518 South Route 31 Suite 200
> > > > > McHenry, IL 60050
> > > > > www.cadzation.com
> > > > > Providing Industrial Strength
> > > > > PDF & DWF Solutions to the
> > > > > Global CAD Marketplace.
> > > > >
> > > > > "Stefan Lindberg" wrote in message
> > > > >
news:11694471.1087379726568.JavaMail.jive@jiveforum1.autodesk.com...
> > > > > > I have Published a MAP drawing with datalinks attached to
objects
> > and
> > > > when
> > > > > I open the DWF file in Composer or Viewer it can take up to 2
> minutes
> > > > before
> > > > > I can select an object and read the attached data. I have tested
> this
> > on
> > > > > different computers and get the same result on every machine.
> > > > > > The DWF file is approx 250 kb and Composer consumes nearly 500
mb
> > > memory
> > > > > for this!! What is the problem??
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>