-
Notifications
You must be signed in to change notification settings - Fork 565
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
Fixing libopenshot version warning message + Sentry.io fixes #4333
Fixing libopenshot version warning message + Sentry.io fixes #4333
Conversation
Co-authored-by: Frank Dana <[email protected]>
json_data: Logs, relative path fix - Lots of log.debug() messages added - project.current_filepath doesn't have a value for new projects, at the point we're saving, so use the 'new_project_assets' context path instead.
Don't make paths to other drives relative
* added guards where we were getting exceptions * added guards where we were getting exceptions * Used setdeafult for safe appending * Made update_color safer while I'm here
…cess app.show_errors in the exception handler, since app fails to initialize.
…ions (Sentry.io errors)
…till possible to change animation interpolations, remove keyframes, etc... on a color keyframe. Double clicking the color still works the same though.
Sentry fixes
…error, since this is a perfectly valid outcome (with the wrong version of blender)
…hot/openshot-qt into fixing-libopenshot-warning-message � Conflicts: � src/classes/json_data.py
@@ -185,8 +185,6 @@ def check_libopenshot_version(self, info, openshot): | |||
}, | |||
level="error", | |||
)) | |||
raise RuntimeError( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was preventing the OpenShotApp from initializing
try: | ||
app = OpenShotApp(argv) | ||
except Exception: | ||
app.show_errors() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
app was never initialized in the except block... and below a few lines, we call app.gui()
which displays the errors... if a gui is created.
Fixing some issues in the release branch, found in my testing and in Sentry.io (with some of our 2.6.0 testers)