After working on this problem for another day, it really seems that 
it isn't possible to print UI Components within a module that exceed 
the screen display.  

The container I want to print is three levels from the application:
 Start.mxml - is application file
 ReportModule.mxml - is a module
 mainContainer is a canvas within ReportModule

I'm using clipContent to remove scroll bars and print the entire 
mainConatiner.  However, the content is always clipped.
- this code is in ReportModule.mxml and is called before the print 
job start

mainContainer.clipContent = false;
this.clipContent = false;
this.parentApplication.clipContent = false;

I'm setting a timer to wait 3 seconds to allow for clipping before 
starting the flex print job.  

Using clipConent on a UI component within the root/application file 
works great.


As an alternative, I'm thinking of creating a bit map object to send 
to the root and then print from there.  But this is a lot of extra 
work.  

Does anyone have a better suggestion?

PS - second issue below has been resolved

Shelley Browning


--- In [email protected], "shelleybrowning" 
<[EMAIL PROTECTED]> wrote:
>
> Hello,
> 
> I've created an application that contains a custom hierarchy 
> chart/drawing (think org chart).  The code for this "chart" is 
> contained in a module.  The size of the container changes based on 
> the # of items in the hierarchy.  I'm having two problems.  
> 
> Printing
> I've seen posts that suggest using clipContent on surrounding 
> containers and the root application, so that items in the 
container 
> that are masked can be printed.  Does this work with modules?  I'm 
> able to get the clipContent concept to work on code within the 
> application, but not if the code is within a module.  
> 
> Redrawing
>      The other issue is that flash seems to "refresh" or "redraw" 
> the container after a while. When this happens the existing 
objects 
> are not removed first.  So the display results in duplicate, 
> triplicate, etc objects in the display.
> 
> 
> Thanks,
> 
> Shelley
>


Reply via email to