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

Autosave path for extra files (JSON, PDF,..) is not respected by normal saves #480

Closed
MAKOMO opened this issue Jun 18, 2020 · 0 comments
Closed
Labels
Milestone

Comments

@MAKOMO
Copy link
Member

MAKOMO commented Jun 18, 2020

Expected Behavior

If an autosave path is set for extra files (eg. PDF) it should also be respected by standard save actions triggered eg. by menu File >> Save

Actual Behavior

The extra files are saved along the .alog file on standard save actions.

Steps to Reproduce the Problem

  1. activate autosave and set two different path for autosave .alog profiles and PDF files
  2. record a profile. On OFF the .alog and .pdf files are generated in the corresponding folders
  3. now save the .alog profile under a third path and see that the PDF is generated next to it

Specifications

  • Artisan Version: v2.4
  • Artisan Build (number in brackets shown in the about box):
  • Platform (Mac/Windows/Linux + OS version):
  • Connected devices or roasting machine:

Please attach your current Artisan settings file (as exported via menu Help >> Save Setings as *.aset) file.
Please attach any relevant Artisan *.alog profiles.

Note that you need either add a .txt extension or zip the files before uploading. Otherwise you will receive a "Not a supported file type" error on uploading.

@MAKOMO MAKOMO added the bug label Jun 18, 2020
@MAKOMO MAKOMO added this to the v2.4.2 milestone Jun 18, 2020
MAKOMO added a commit that referenced this issue Jun 18, 2020
…entries

- updates to MPL v3.2.2
- ensures that extra autosave artefacts are save in the extra autosave path if specified (Issue #480)
@MAKOMO MAKOMO closed this as completed Jun 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant