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
This interface is pretty confusing because it makes users enter exact pixel values. From a human point of view, it's hard to tell the difference between RGB(255, 0, 0) and RGB(254, 0, 0). But the code needs these exact numbers to work right.
It'd make more sense to just use something like "touching sprite."
The performance isn't great either, since it has to pull images from the GPU or go through each pixel one by one.
In short, we don't really need this function, so it should probably be removed.
@JiepengTan It was added for compatibility with the Scratch API Touching Color. Therefore, we need to retain it to make it possible to do auto-transforming from Scratch project to spx project.
While I agree with the points you mentioned above, it isn't an API we recommend to use in standard spx projects.
This interface is pretty confusing because it makes users enter exact pixel values. From a human point of view, it's hard to tell the difference between RGB(255, 0, 0) and RGB(254, 0, 0). But the code needs these exact numbers to work right.
It'd make more sense to just use something like "touching sprite."
The performance isn't great either, since it has to pull images from the GPU or go through each pixel one by one.
In short, we don't really need this function, so it should probably be removed.
The text was updated successfully, but these errors were encountered: