You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Funny:
if I plugin-fork a shader that was shadertoy-forked, then the new mentioned shadertoy-fork link is wrong. see here: https://www.shadertoy.com/view/sdt3Dl
Maybe ref is somehow shader #0000: it is https://www.shadertoy.com/view/4sfGRn created by iq in 2013-01-02, within all the first shaders he created when opening Shadertoy. ;-)
Now, what should be done with this ref ? 2 possibilities:
updating the fork target ref
deleting the shadertoy-fork information.
I would personally tend to prefer the second. because I really prefer your version of the feature (which already keep track -correctly - of the parent), and I often use fork to start almost-fresh-shaders for which it would make little sense to keep-track of the link.
The text was updated successfully, but these errors were encountered:
Funny:
if I plugin-fork a shader that was shadertoy-forked, then the new mentioned shadertoy-fork link is wrong. see here: https://www.shadertoy.com/view/sdt3Dl
Maybe ref is somehow shader #0000: it is https://www.shadertoy.com/view/4sfGRn created by iq in 2013-01-02, within all the first shaders he created when opening Shadertoy. ;-)
Now, what should be done with this ref ? 2 possibilities:
I would personally tend to prefer the second. because I really prefer your version of the feature (which already keep track -correctly - of the parent), and I often use fork to start almost-fresh-shaders for which it would make little sense to keep-track of the link.
The text was updated successfully, but these errors were encountered: