Add possibility to open a JASP file with other data files and report results #6025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JorisGoosen
reviewed
Sep 25, 2025
Desktop/data/fileevent.h
Outdated
| _last_error = "Unknown error", | ||
| _message; | ||
| bool _completed = false, | ||
| bool _started = false, |
Contributor
There was a problem hiding this comment.
an enum (via DECLARE_ENUM) describving the state of the fileevent is better
boutinb
force-pushed
the
changeDataFile
branch
2 times, most recently
from
098ef8d to
cc20558
Compare
boutinb
force-pushed
the
changeDataFile
branch
from
c0f0818 to
ae62db7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds the possibility from the command line to run analyses with other data files and export the results in PDF or HTML.
For this the command line supports extra options:
JASP <JASP file> (<data file 1> <data file 2> ...) --inputDataDir <path to folder> --outputDir <path to folder> --outputPdf --dontExportResult --keepJASPOpen--outputPdfis specified). The export file is generated in the same folder as the data file, or in the folder specified by-outputDir. This step can be discarded if-dontExportResultis specified.--keepJASPOpenis specified.To realize this, the argument parsing of the main function has been rewritten and uses now a ParsedArguments object.
Also the handling of the FileEvent has been partly refactored: it has now a status property that states whether the event is
initialized,started,completedandfinalized. All the File Events follow now the same process, and are also deleted at the end (they were not deleted before). By making the process clearer, event chaining is now possible without risking that one handling of the first event does mangle with the handling of the second event. This was needed to start the synchronization of the data file only when the JASP file is completely opened.I have also added the possibility to drag and drop a data file to a JASP instance, so that it synchronizes directly the analysis with the new data.