Our pure JavaScript Scheduler component


Post by oriswid »

Hello.

Is there a way to expand the view of the the export to take entire page?
At the moment it takes only half a page.
It is ok if the pdf will be split to multiple pages as long the entire page is full.

I attached an example of the current result.

this is the current config for the export :

{
  exporterType: 'multipage',
  fileName: 'Plataine-scheduler',
  fileFormat: 'pdf',
  orientation: 'landscape',
  scheduleRange: 'currentview',
  repeatHeader: true,
  sendAsBinary: true,
  }
Attachments
Plataine-scheduler (5).pdf
(53.12 KiB) Downloaded 49 times

Post by marcio »

Hey oriswid,

You're using the scheduleRange: 'currentview', option, which you can see in the documentation https://bryntum.com/products/scheduler/docs/api/Scheduler/feature/export/PdfExport#config-scheduleRange

currentview - Currently visible time span

If you change to completeview that would change the export result for what you desire I believe.

Please let us know if that worked for you.

Best regards,
Márcio


Post by oriswid »

Hey Marico.

Thank you for the replay... this is not what I intended.
I want to render the current visible Time span. But as shown in the attached file, the render only takes half the page...

We need the PDF to be rendered in the entire page (top to bottom). it does not matter if it will take more pages to render.


Post by alex.l »

Hi,

Do you see this problem with the code of our examples? https://bryntum.com/products/scheduler/examples/export/
How to reproduce this?

All the best,
Alex


Post by oriswid »

Hey Alex

in order to reproduce - use the setting as in the original post and try to print a scheduler that has only 3 rows.
at the moment the Demo does something similar... you print multiple rows and all of them are shown but the export function only generates half a page - the content does not take 100% of page width.
this can be solved by increasing the size of the content.


Post by alex.l »

Hi, thanks for clarifying! I reproduced that. Here is a ticket https://github.com/bryntum/support/issues/6990
You can subscribe on ticket updates to be notified when it's done.

All the best,
Alex


Post by oriswid »

Hi Alex.

Any news about the issue?


Post by tasnim »

Hi,

Thank you for your inquiry. We understand how important this is for you, but we have a lot on the list. So this bug is not in the list of nearest releases. We are now pushing it to 5.5.0.

We apologize for any inconvenience this may cause and appreciate your understanding. Please rest assured that our team is actively working on a solution, and we value your feedback in helping us improve our product.

If you have any other questions or concerns, please don't hesitate to reach out to us. We're here to assist you in any way we can.

Thank you for your patience and continued support.

Warm regards,
Tasnim


Post Reply