ShaderToy-Chrome-Plugin icon indicating copy to clipboard operation
ShaderToy-Chrome-Plugin copied to clipboard

[BUG] plugin-fork of a shadertoy-forked : bad ref

Open FabriceNeyret opened this issue 3 years ago • 0 comments

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.

FabriceNeyret avatar Sep 06 '21 08:09 FabriceNeyret