Since the "activeThreads" thread filter, depends on the dimensions of the output data, it makes sense to be able to ask the WriteDeviceFunction for that information.
We keep the activeThreads parameter in the Source versions of the Read and ReadBack Device Functions, because we may want to use less threads in the "z" axis in some ocasions. So, we allow for the user to have the final word on "activeThreads" values.
Since the "activeThreads" thread filter, depends on the dimensions of the output data, it makes sense to be able to ask the WriteDeviceFunction for that information.
We keep the activeThreads parameter in the Source versions of the Read and ReadBack Device Functions, because we may want to use less threads in the "z" axis in some ocasions. So, we allow for the user to have the final word on "activeThreads" values.