Signature controllers only have access to the background image URL and the new base 64 encoded image. This makes it very difficult to map the edited image to a specific object. Currently, capturing signatures in multiple locations requires each location to have a dedicated controller. Even this can't always be done though as capturing signatures for each element in a list has no way to specify an index and a controller for each element is not possible.
Could a configurable parameter be added to pass some kind of context key through the controller so that it could be mapped back to an object in the model?
Signature Controller Limitations
-
- Posts: 178
- Joined: August 31st, 2021, 11:37 am
- Contact:
-
- Posts: 329
- Joined: August 26th, 2021, 9:18 am
- Contact:
-
- Posts: 571
- Joined: August 26th, 2021, 9:56 am
- Contact: