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
At the moment, model-to-view and view-to-model position mapping use first the default algorithm and then additional callbacks may be fired and alter the position calculated using default algorithm.
This behaviour sounds okay, but is a problem in List feature because for some list structures the default algorithm throws.
Hence I propose that default algorithm should be used only if no custom callback has been used.
The text was updated successfully, but these errors were encountered:
Other: Default conversion.Mapper position mapping algorithms are now added as callbacks with low priority and are fired only if earlier callbacks did not provide a result. Closes #884.
BREAKING CHANGES: Since default position mapping algorithms are attached with low priority, custom position mapping callbacks added with higher priority won't receive position calculated by default algorithms in data. To execute default position mapping algorithms and use their value, hook custom callback with lower priority.
At the moment, model-to-view and view-to-model position mapping use first the default algorithm and then additional callbacks may be fired and alter the position calculated using default algorithm.
This behaviour sounds okay, but is a problem in
List
feature because for some list structures the default algorithm throws.Hence I propose that default algorithm should be used only if no custom callback has been used.
The text was updated successfully, but these errors were encountered: