Currently only the most common properties can be directly configured from the Picker or its controllers without subclassing.
NBUCameraView, NBUCropView, etc., many more properties and some are "forwarded" from the controller but it will be ugly and hard to maintain to just reproduce every property there.
One possible solution would be to have a dictionary of keyPaths and values to be applied as views get loaded.
Currently only the most common properties can be directly configured from the Picker or its controllers without subclassing.
NBUCameraView
,NBUCropView
, etc., many more properties and some are "forwarded" from the controller but it will be ugly and hard to maintain to just reproduce every property there.One possible solution would be to have a dictionary of
keyPaths
and values to be applied as views get loaded.Related to #2.