closed
Public

I am prototyping an interface where a common tab widget is used on all pages. To simplify matters the tab widget is put in a master page and Go To page-event is used when the tab selection changes. This works great for simulation.

The problem is exporting to PDF. All pages comes with the default tab selection which is confusing. I tried adding page loading events to set the tab selection correctly for each page, but this is not honored when exporting to PDF. Any suggestions?

1 answer

Good question. True it is a limitation of the current PDF export: the export is too static. We will investigate the way to improve this later.

#1
  1. Not knowing your implementation a separate page level Export event might be useful. It would only need a "Operate on Element"-action since it is all about widget appearance. This would then apply both to image and PDF export.

This question is now closed