My crosstab looks fine in the web viewer but when I export to PDF it's clipping it like showin in the image. It's also making the columns much wider than they need to be. (The web version isn't doing that.)
Does anyone know how to fix it? I tried searching for an answer and didn't see anything.
Without seeing the parameters you're passing to your RenderTask it is hard to tell exactly, so I'm going to guess that you have PAGE_OVERFLOW set to CLIP_CONTENT rather than FIT_TO_PAGE_SIZE.
A note of caution though. This discussion on the Eclipse forum mentions that page-break interval settings might override the page size render options. Note that the OP on the linked discussion was having a problem with the PDF exported from the HTML viewer.
EDIT: according to the docs inside genReport.sh you are able to pass parameters on the command line (-p pageOverflow=FIT_TO_PAGE_SIZE) or you can create a parameter file (-F params.txt)
It is unclear to me whether you can pass the constant (FIT_TO_PAGE_SIZE) or must pass its expected value (2), so you might have to try both.
I think you have restricted the width/height of your report
goto Master Page then click on the general settings and there you find the type drop-down choose Custom.
Through this custom options you can give your own height/width of your report and too in the report layout.By doing this you can expand your report width
NOTE: The master page width should equal to the width of your layout.
Related
everyone.
I am working with Oracle Reports 6i to generate a report that includeds text in the form of paragraphs. Everything looks fine from the Real Time Viewer however when the report is run to generate a PDF, some, of the paragraphs would change from Justified to Filled.
This doesn't happen for every text container. In a full page I will have two paragraphs that are filled instead of justified.
Here is the details.
Each paragraph is within their own container.
The alignment for all containers is set to Justified(Flush)
Paragraphs have the same font type and font size.
I have already try the size of the output but it didn't make a difference. Is there any configuration parameter or any format function I can use to fix this?
Thank you all!!
If some paragraphs are OK and some are not, I'd suggest you to use good, old copy/paste principle:
delete wrong ones
copy correct one
paste it
edit its contents - hopefully, it'll look OK (as all properties the "correct" one had are now "inherited")
I have 2 questions need your help.
I would like to add a button on each plot to be a setting button. I use label with event listener and it works well ( as shown in attached file). However, my client asked me to change from normal text to graphic icon? How should I proceed?
As you can see from the attached image, the third plot is macd series. The value rage is from -3e-8 to 3e-8 (by my observation). I manually set the maximum and minimum, and it get incorrect scale as shown.
How should I set the maximum and minimum for yScale?
I don't know how to get maximum and minimum value from a series. Can you suggest me?
A1 – Unfortunately, the current version of AnyChart doesn't provide an opportunity to add custom-made buttons inside the chart. But you can use a trick and use stage based layout. It means that the container includes a stage. The stage includes the stock chart all other elements by layers. Using this approach you can place an image (icon) upon the plot and set a listener just as for the 'settings' label.
For details, please, check the sample in the comment below.
A2 - We are planning to fix this behavior in 8.4.2 update (approximately by the end of November 2018).
I will notify you when the fix becomes available.
As a temporary workaround, you can get min /max value from your MACD indicator. For details, please, check the sample in the comment below.
You can apply min/max to the yScale of plot #0 like this:
chart.plot(0).yScale().minimum(minValue);
chart.plot(0).yScale().maximum(maxValue);
We are glad to inform you that we have released 8.4.2 update which brings many fixes and improvements. This update also includes a fix on the issue you reported. Now calculation of min/max of Y-scale works properly with small values. Update your binaries to get the fix.
When displaying a box graph, pygal displays values outside of the normal zones. You can see the example on their site as well:
You'll notice that no values are above 16,000 or below -4000 (in fact none are below 0). It just doesn't display properly.
This is posted for anyone who doesn't look on the website for answers (which I don't usually).
There is a solution to this problem, and it is not resolved completely yet - but there is a quick fix.
In the meantime, to make it work (as expected) instantiate the object like this:
box_plot = pygal.Box(mode='extremes')
You'll notice that the above example will be solved, and in fact to my knowledge this is the only way to make box plots work.
To follow the issue: Link to the issue request
I am using telerik reports. Some of my reports are large sized. When printing these reports not fit into default page size. I need to fit it into page by default. How can I implement this? Pls reply
Each report has a defined size in its definition which you can change and the same goes for page margins. You should also have in mind that each printer has hardware margins which is not possible to override. With that taken into account, you should be able to set an appropriate size that prints correctly. If still in dilema, elaborate on the report size, its pagesettings and the printer and paper format you're trying to print to.
I have text objects on a Crystal Report in Visual Studio with an initial capital. When I print the report, the text is all lower case.
And the reason is?
We have found a workaround for this problem. Not sure how this works :) - can any expert explain?
We found that this problem of case change was happening whenever the extent of text within any page / section of the report was going beyond the settings of the page size minus gutter, left/right margins, top/bottom margins set for the report.
As a workaround, we have asked all our reports developers to keep the text (for A4 size reports) to within 7.5 inches X 7.5 inches. The problem does not happen when this is adhered to.
Would definitely like to know exact reasons for the misbehavior though.
This might be affecting by some of the settings.
But if you go and edit the field , you can see it automatically change to lowercase.
If you agains change it back your case, then it will work fine.
It looks like it happend for one time. To be honest, I don't know why this happend