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

Unknown behaviour if the mxd from a previous version is deleted. #94

Open
andrewphilipsmith opened this issue Jul 17, 2020 · 1 comment
Labels
question Further information is requested

Comments

@andrewphilipsmith
Copy link
Member

To check:

  • Create a map - let it produce an mxd (v1) and a pdf (v1)
  • Delete mxd v1 (this will trick the tool into thinking that the version available version number is v1)
  • When it comes to export the pdf, how will it handle the fact that pdf.v1 already exists?

Desired behaviour

  • I would like it to handle this gracefully please.

Actual behaviour

  • Unknown
@andrewphilipsmith andrewphilipsmith added the question Further information is requested label Jul 17, 2020
@sidhanthapoddar99
Copy link

sidhanthapoddar99 commented Mar 14, 2021

Hi @andrewphilipsmith can this issue be solved by renaming the old pdf.v1 or maybe overwriting the old pdf.v1 with the new pdf.v1
alternatively, if an error needs to be generated
can a try condition be used to check for the existence of pdf.v1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants