Thats awesome dude thanks for that, points not pixels, always thought the points in processing related to pixels. gotta pay more attention. anyway that works a treat, i suppose it is best used as a final play, meaning build the program using height and width then once it is finished you enter the import and the exit along with pdf specs. As in your handy as, program above. very cool means. Still I must ask while I have you guys at hand , this I see will not allow me to view the program (macbook 4gb is what i use) It seems to save perfect as like I asked. Still I must ask is there anyway to save large saveFrame() files from active programs? p.s. thanks for above if you dont know answer to new question off hand dont worry yourself, I will figure it out in time. 

your on about saving as usual with the save() and just saving as .png. That also works only thing is it saves it as 72 pixels per inch, where the .pdf approach saves it a a perfect 300pps. So the above approach shared by massimo is much better way to save static prints off a large sized program and no need for the "strokeWeight as 1/posterScale" Which in truth dude, i am cant follow. I recommend using  import processing.pdf.*; approach. Now the mission is to find out if this can be used to save frames at a particular time in active programs.

But when you do that, you can't use OpenGL because the picture gets cut off. :/