-
Notifications
You must be signed in to change notification settings - Fork 595
(Fix-or-)Revert "Effect parenting" #4169
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
Conversation
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.
I just noticed that in develop
dragging a clip to timeline freezes the program. This isn't happening in develop~1
. So a revert seems in order.
That I'm not seeing, I don't think... do you mean dragging from the Project Files list, or dragging in a media file directly from the OS? Is your libopenshot build up to date? There were corresponding changes merged there recently, if you haven't built a most-current libopenshot that could cause issues. (It's also a good idea to blow away the |
Heh. In fact, I think that's what took down the previous CI run; the CI builds here use the Ubuntu PPA packages as their source for libopenshot-audio and libopenshot, and yesterday those packages were still a day out of date. I've ensured that they're now regenerated, so we'll see if this unit test run goes any better... (ETA: It did not. Something weird is going on with the CI runs, but I don't think it's our code. Runs fine for me locally. Still investigating.) |
Solved it, PR building in libopenshot |
(The build issue, I mean. The properties thing is still a problem) |
Turned out, there were some issues caused by those aforementioned libopenshot changes, which I fixed last night in OpenShot/libopenshot#683. Anyone using the Ubuntu PPAs or building their own libopenshot should update to fix the Python bindings, which affects OpenShot. |
That was FINALLY fixed in CMake 3.20, btw. |
This issue, OTOH is fixed by my recent optimized-saving PR (don't have the # handy), which will make this revert unnecessary when merged. That's looking likely enough at this point that I'm going to close this as solved. |
Reverts #4058
I don't actually want to revert this. However, it needs to be fixed or reverted.
As I warned in review, the change to the
properties_model.py
breaks the optimization of undo/redo functionality. Previously, changing thelocation_x
parameter of a clip produced this undo entry:After the merge, that same change results in this being inserted into the undo list:
The same is true for any change to any property. That's not an acceptable regression.
cc: @jonoomph @BrennoCaldato