-
Notifications
You must be signed in to change notification settings - Fork 362
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
New Addon: Asset Conflict Resolution Dialog #7232
base: master
Are you sure you want to change the base?
New Addon: Asset Conflict Resolution Dialog #7232
Conversation
Co-authored-by: Samq64 <81489795+Samq64@users.noreply.github.com>
Related thing that used to exist in 2.0 (basically you could just clear and then import into the costume): #5083 |
Does this possibly also resolve that issue? It's not the desired design but it solves the same issue and potentially better as long as the names are the same. |
The import button in 2.0 would add the uploaded thing to the costume instead of replacing, but you had to clear it first to do this, so they're a bit different. There was also the add button in 2.0, which was similar but you would select costumes/backdrops from the library instead. |
I haven't looked at the objects but a simple solution that should work most of the time would be checking if |
The assetObj has a very tell tale signature when it's a new costume, just checking if it's the same for sounds right now. Don't want to use the name for sure. |
I tested this more extensively and found no bugs when using the sprite folders addon. As far as I am aware this works as expected. |
No dialog if I drag in a conflicting costume from the backpack edit: Pretty sure that worked before so think it's related to the check for if someone pressed the new costume button (did not look) |
Oof... nice catch |
As Garbo hinted at this is probably a side effect of the previous fix. I tested quite a few ways of adding the costume and thought the signature was specific to the new costume, but it's possible dragging from backpack has the same signature. |
Dropping files onto the backdrop pane or uploading them outside the costume editor doesn't trigger the dialog. |
Will fix when I have some free time |
I can reproduce the first thing, but I don't understand what you mean by the second. Could you please clarify this? Edit: Was able to replicate the second part |
Making it work for the backdrop was quite easy. It is unfortunate Scratch chose to have a separate add backdrop function. |
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 haven't taken a full look at all the code but drag and drop, sounds, backdrop and HD uploads all work fine.
…/ScratchAddons into file-conflict-dialog
Resolves #7177
Changes
asset-conflict-dialog.mp4
Reason for changes
For projects with assets created via external editors, it is often neccessary to replace the existing costumes with updated versions. Currently you need to delete the old ones, then import the new ones. This is tedious, so this accelerates that process.
Tests
I have tested: