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
Some processes require more appropriate parameters than simple 'int' and 'double', etc.
It is very frustrating to try to work around this limitation.
For example, some processes might need to compute something on an array in a mesh.
We could simply pass the array name as parameter to the process.
Instead, we are forced to pass 2 integers: the field data type (cell, point or field data)
and its index in the 'array of arrays' .
In pipelines this is problematic as we might not have access to this information, and its unintuitive.
Thus this requires to implement "helper" methods, that find the array for us and then call the process
with the correct parameters.
If we are to add more overloads to setParameter, it should be done in dtkAbstractProcess, not medAbstractProcess, or it will cause confusion amongst developers not familiar with how overload and override resolution works in C++.
Some processes require more appropriate parameters than simple 'int' and 'double', etc.
It is very frustrating to try to work around this limitation.
For example, some processes might need to compute something on an array in a mesh.
We could simply pass the array name as parameter to the process.
Instead, we are forced to pass 2 integers: the field data type (cell, point or field data)
and its index in the 'array of arrays' .
In pipelines this is problematic as we might not have access to this information, and its unintuitive.
Thus this requires to implement "helper" methods, that find the array for us and then call the process
with the correct parameters.
Could be related to #370
tl;dr: Need setParameter(QString, [...]), setParameter(void*, [...])
The text was updated successfully, but these errors were encountered: