You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by hferreira <hf...@gmail.com> on 2018/01/04 11:15:59 UTC
Print issue between applications with the same component
Hello,
When I print from my TLF editor component isolated on a Window test
application, I got this beautifull result:
https://www.dropbox.com/s/cdmwnsasemvqqff/2.pdf?dl=0
However when I added this component to an older bigger application, I got
this result: https://www.dropbox.com/s/m2xldpsonih0t3c/1.pdf?dl=0
It's the same Flex framework and AIR version and the issue seems that it's
not filling the all page. Perhaps it's related to the AIR xml configuration
or something else but it's difficult to see on a bigger application.
Anyone knows any specific configuration (AIR xml for example) that can
influence the print job (I don't have any change on the DPI on the AIR xml)
or a tip that I can start to explore ?
--
Sent from: http://apache-flex-development.2333347.n4.nabble.com/
Re: Print issue between applications with the same component
Posted by hferreira <hf...@gmail.com>.
Alex,
Thank you so mutch !
That's the fact, the background.
The thing that was confusing me, was that in a demo application seems
(false/positive) that was perfect and one a production one we saw than gray
background but turns out that the demo app had a white background !
I changed the window background color of the demo application and I got 2
identical results.
Now, it's a metter of adjustments to fill completly the print area as you
mentioned.
Thank you very match for the tip !
--
Sent from: http://apache-flex-development.2333347.n4.nabble.com/
Re: Print issue between applications with the same component
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Ah, ok, it looked like browser chrome...
IIRC, this has to do with the display object that is being printed and its
size relative to the print area. If the display object does not have a
background or that background does not fully cover the print area then you
haven't really specified every pixel in the print area. Sometimes the UI
shows some content inside of a container with scrollbars, etc, and if you
print the container you'll print the scrollbars, but if you print the
content, the content may not be the right size or is relying on the
wrapping container to draw the background.
HTH,
-Alex
On 1/4/18, 10:59 AM, "hferreira" <hf...@gmail.com> wrote:
>On the second url you can see a large gray bar on the right and also on
>the
>bottom (also a thin line on the left).
>Seems that is empty space so perhaps a bug on FlexPrintJob.
>
>I will debug on the 2 window applications to see if there is any
>difference
>and try out to find the origin of the issue.
>
>
>
>--
>Sent from:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.2333347.n4.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7
>C7b33e907400645d9f51608d553a5407d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7
>C0%7C636506891792280085&sdata=VF3ZN2fCHJ0qTSVxx%2FyCYkOewIUcBlKMdW8OzvPbmB
>k%3D&reserved=0
Re: Print issue between applications with the same component
Posted by hferreira <hf...@gmail.com>.
On the second url you can see a large gray bar on the right and also on the
bottom (also a thin line on the left).
Seems that is empty space so perhaps a bug on FlexPrintJob.
I will debug on the 2 window applications to see if there is any difference
and try out to find the origin of the issue.
--
Sent from: http://apache-flex-development.2333347.n4.nabble.com/
Re: Print issue between applications with the same component
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Hugo,
To my eyes, I cannot see a difference between the two. What is it that
you are seeing?
-Alex
On 1/4/18, 3:15 AM, "hferreira" <hf...@gmail.com> wrote:
>Hello,
>
>When I print from my TLF editor component isolated on a Window test
>application, I got this beautifull result:
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.dropb
>ox.com%2Fs%2Fcdmwnsasemvqqff%2F2.pdf%3Fdl%3D0&data=02%7C01%7Caharui%40adob
>e.com%7C4f31b760539a4e0bf5ee08d553648d30%7Cfa7b1b5a7b34438794aed2c178decee
>1%7C0%7C1%7C636506613694818370&sdata=VH9s30DvlTr4asbiLzIjFrX5p%2Fm8uWMTU%2
>BugktlKqTQ%3D&reserved=0
>
>However when I added this component to an older bigger application, I got
>this result:
>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.dropb
>ox.com%2Fs%2Fm2xldpsonih0t3c%2F1.pdf%3Fdl%3D0&data=02%7C01%7Caharui%40adob
>e.com%7C4f31b760539a4e0bf5ee08d553648d30%7Cfa7b1b5a7b34438794aed2c178decee
>1%7C0%7C1%7C636506613694818370&sdata=vzpVrIIkI2DmxXLabC%2FlHJ7%2BwHv1s%2BJ
>SdvFQyOqxdkc%3D&reserved=0
>
>It's the same Flex framework and AIR version and the issue seems that it's
>not filling the all page. Perhaps it's related to the AIR xml
>configuration
>or something else but it's difficult to see on a bigger application.
>
>Anyone knows any specific configuration (AIR xml for example) that can
>influence the print job (I don't have any change on the DPI on the AIR
>xml)
>or a tip that I can start to explore ?
>
>
>
>--
>Sent from:
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-fle
>x-development.2333347.n4.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7
>C4f31b760539a4e0bf5ee08d553648d30%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7
>C0%7C636506613694818370&sdata=cE8yvDL%2FQBRwCT1qSmaeOvkEA%2B8SxaDQkAlYYKqJ
>l2Y%3D&reserved=0