-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python Bindings Known Issues #913
Comments
|
Pipeline Objects
The last line in this python will fail because not all of the arguments are present in the |
Pipeline FilterThere should be easier access to the "human_name" and the "name" attributes for the Pipeline filter, i.e., a developer should not have to jump through pipeline_filter.get_filter().human_name()
|
C++ Filter NamingAll filters should end with "Filter" |
PreflightUpdatedValues
In the Python Filter, one cannot return preflight updated values. The following does not work, throwing an error about supported types.
Progress Messages:
This does not work because ProgressMessage is not exposed
DataStructure API Additions
AttributeMatrix API Additions
|
Breakdown the API into more namespaces
This is Non-Trivial. Putting a pin in it for now. |
- Some changes are for #913 - No longer require name argument on `Pipeline.to_file` - Added `Pipeline.to_json_str` - Added `Pipeline.name` - Added `PipelineFilter.comments` - `IFilter::toJson` now uses default values when the value in the arguments doesn't exist instead of failing - Fixed the lifetime of docstrings generated at runtime - Removed `registerPluginPyFilters` Signed-off-by: Jared Duffey <[email protected]>
- Some changes are for BlueQuartzSoftware#913 - No longer require name argument on `Pipeline.to_file` - Added `Pipeline.to_json_str` - Added `Pipeline.name` - Added `PipelineFilter.comments` - `IFilter::toJson` now uses default values when the value in the arguments doesn't exist instead of failing - Fixed the lifetime of docstrings generated at runtime - Removed `registerPluginPyFilters` Signed-off-by: Jared Duffey <[email protected]>
Actions need to be documented
@imikejackson
There is currently NO documentation for each of the actions.
Filter Parameters Documentation
@imikejackson
Each Parameter should have a screen shot from the User Interface to help the user identify the parameter
IDE Filter Documentation
@imikejackson
Update the .pyi files to include first paragraph from filters documentation
The text was updated successfully, but these errors were encountered: