Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

print composer - ability to run python before / during / after export + api #23648

Open
qgib opened this issue Oct 19, 2016 · 1 comment
Open
Labels
API API improvement only, no visible user interface changes Feature Request Print Layouts Related to QGIS Print Layouts, Atlas or Reporting frameworks

Comments

@qgib
Copy link
Contributor

qgib commented Oct 19, 2016

Author Name: Jesse McMillan (Jesse McMillan)
Original Redmine Issue: 15726

Redmine category:python_plugins


Adding the ability to run custom python functions in the print-composer export process would allow for additional automation of workflow.

For instance, I have a 200+ page atlas for print. When exporting I also need to update an online database and upload the exported PDF. I would love the ability to use a python script to grab the file that was just exported, upload it, and run some mySQL updates via python as well.

So to summarize, I would like an option to run custom python before or after export.
If running after, an api that provided access to the file that was just exported and the atlas feature data would be useful.

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • easy_fix was configured as 0

@alexbruy alexbruy added API API improvement only, no visible user interface changes Print Layouts Related to QGIS Print Layouts, Atlas or Reporting frameworks and removed Plugins labels Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API API improvement only, no visible user interface changes Feature Request Print Layouts Related to QGIS Print Layouts, Atlas or Reporting frameworks
Projects
None yet
Development

No branches or pull requests

2 participants