my environment is SQL 2005, SSRS 2005 , .net 2.0
Client is experiencing following issue on two different printers. ( Canon and Lanier LD140).
We have a report which is designed as landscape report.
When report is send to print,
First page is rendered in portrait mode(cutting of the information on the right side. )
rest of the pages print in landscape mode.
did anyone have similar issue and knows how to fix it so first page gets printed in landscape mode?
thanks.
We tried printing on other printers and it worked fine.
Issue was later resolved for printers in questions by updating their printer drivers.
Related
I have deployed a personal flutter-web project on firebase and the responsiveness is working fine. As in when the website is opened on a laptop it shows a UI specific for large screens and when it's opened on the mobile phones (chrome browser) it shows UI for mobile screens.
Now the problem is, whenever I check "Desktop Site" in the chrome browser, I get the UI that is meant to be shown for larger screens which is okay, but it looks stretched vertically, and the appbar at the top is also not visible.
so my question is,
Is there a way that I could check whether browser's desktop-site mode is ON?
or any other way that I could just make the website look like a zoom-out version of web UI whenever desktop-site mode is ON?
We were not shown the code. Therefore, it is difficult to say for sure. But I had such problems when I ran the application building without parameter --web-renderer
flutter build web
The point was that by default it uses different renderers (CanvasKit for desktop and HTML for mobile). And since I used things that required CanvasKit, the application in mobile browsers was displayed incorrectly.
Building with the appropriate parameter solved my problem
flutter build web --web-renderer canvaskit
I had built MS teams tab in Angular using angular material all over, but as seen below the dropdown is showing some unusual working.
This is only coming on Android mobile. Something specific needs to be fixed or its the behaviour of MS teams?
works correctly in iOS MS Teams app:
I have successfully replicated the issue in Android devices.
So, there was horizontal scrolling which was creating the problem on the Android devices but after removing that it worked. But it was very strange as this same thing didn’t give me an issue on iOS devices.
i'm trying to print an invoice from an ASP.NET application to an Epson LX 300+. The problem i have is that i cannot use traditional ReportViewer because printing icon only works on Internet Explorer, the users use Mozilla and Chrome.
We tried to render a HTML page for the invoice and print, but horizontally is reduced around a 50%.
So we are trying create a ReporViewer and export it to a PDF, then open it using PDF.js... the result is the same horizontally 50% less.
The page size is Statement. I'm attaching 2 images printed from the PDF.js
I've noticed if we vary the resolution of the printer, it's 90% horizontally, but also changes the vertically.
Your help would be really appreciated. Regads. Also We tried on Chrome but its really fuzzy.
Printed from PDFjs on Mozilla 120x72dpi
Printed form PDFjs on Mozilla 120x144dpi
When scrolling down through a recently deployed SSRS report, the columns become jumbled and I am unable to scroll all the way to the bottom. I have adjusted the zoom of my browser but this has no effect. The attached screen shot is what my report looks like on the site while scrolling. I have tried Chrome and IE. Chrome is my go to for the reports.
Found out the problem, the details row was also set to true for FixedData. I set it to false and everything works fine
I'm developing an MVC based web page for a small business.
I've never come across this before...
On my laptop screen and my external monitor, the formatting is fine, however one of the guys in the office has shown me that the text is just writing out of the box in --> direction, so much that it's even adding a horizontal scroll bar!
---------------EDIT---------------------
ISSUE RESOLVED
Thanks to #Geeo
Turns out the problem was IE Compatibility mode - set to IE7, changing it to IE9 appears to do the trick.