Flex printing: why am I getting two different printing UIs? - apache-flex

I'm starting to play with printing in Flex. I tried to run the "Example: A simple print job" here from the Adobe web site and then by building the same app in FB4 and running it in chrome. Interestingly, the printing UIs I get look different (see picture). Is this because the example online is built with FB4.5 and I'm using FB4, or is it something else?
Note: I'm using Chrome on Windows 7.
thank you!

Related

How to debug "Aw, Snap!" Chrome (when opening multiple tabs)

If I ctrl-click a link in my app and open ~10 tabs, for 2-3 of them I get the
I have no idea where to start investigating this 🤷
I am working on ASP.NET (.NET6) MVC + Knockout, dunno if this is relevant.
Looks like a memory leak of some sort, that Chrome can't handle.
Chrome Error code: STATUS_BREAKPOINT
Edge (also based on chromium) Error code: STATUS_ACCESS_VIOLATION
Try making sure Chrome has all the permissions, also make sure you singed in before you started using it. If this doesn't work. Unistall it and install it again. If you have the same problem. Debug it with Python/Pycharm. Hope it helps.

Handling variable-fonts when printing a webpage to PDF using Chrome

I'm working on a webpage that has a different "print to PDF" result (after Ctrl+P -> Save to PDF in Chrome) than the original web display by using #media print in the CSS code.
I'm using a variable font with the parameter font-variation-settings:"wght", but the generated PDF seems to ignore this parameter when used in #media print.
Yet, when using the Chrome tool "Inspector>Rendering>Print emulate CSS media type", changes of this parameter are taken into account in the displayed web page!
Looks like the problem comes from the Ctrl+P interface, any ideas on how to handle this?
Thank you in advance.
Please see https://bugs.chromium.org/p/chromium/issues/detail?id=1070089 - this should be fixed now, you may want to retest with a recent Chrome Canary build and see if the issue is indeed gone.

Crystal Reports does not print correctly in Firefox

I am using the CrystalReportViewer in a ASP.net application using VS 2010. The reports were built using CR version 2011.
When printing in firefox a bunch garbage is printed out.
The print works fine in IE and Chrome. Any idea how to make firefox print correctly?
I have the same problem and the only idea I can come up with thus far is to trap the printing on server-side, then use crystal reports object to do the printing. I know its a hack, but it seems to be the only way right now.

Flex Mobile App StageWebView Printing

I have an iphone app developed in Flash Builder/Flex Mobile Project that displays PDFs using stagewebview.
I am interested in printing these PDFs from the application. Does any one know if this is possible and if yes could you please suggest some example code?
Thanks!
AlivePDF did you have a look on this.
http://livedocs.adobe.com/flex/3/langref/mx/printing/FlexPrintJob.html
http://www.adobe.com/livedocs/flash/9.0/ActionScriptLangRefV3/flash/display/BitmapData.html
With this you can read pixel by pixel and send to printer to print the Object.

Images do not display consistently between VS and debugging version

I have a GridView with three Button columns that are set up with images. When I select my path for the image, using the GUI tool that VS provides, the resulting path is something like ~/Images/myicon.png and the image displays fine (sometimes) in the VS Design mode. But the images do not display on the running version of the website (using Firefox) because the image locations resolve to ../Images/myicon.png. I can manually change it to Images/myicon.png and it works fine on the website but then not in VS.
How do I get them to behave the same way? These file paths are driving me nuts!
I would use paths that work in FireFox. Forget trying to get things to display in design mode, in VS 2005. Design mode is 2005 is really horrible.
Honestly, design mode can not be relied upon for styling, anyhow, in any version. It can come close now in VS 2010, but ultimately, it will never be as good as displaying the markup in a browser.

Resources