Support splitterTarget property #11
Labels
Comments
bertfrees
pushed a commit
to sbsdev/dotify.formatter.impl
that referenced
this issue
Feb 24, 2020
* brailleapps#4: Parsing of toc-entry-on-resumed elements. * brailleapps#4: toc-entry-on-resumed elements: parsing fixed, unit test added. * brailleapps#4: toc-entry-on-resumed works for volume-ranged TOCs * brailleapps#4: Implemented toc-entry-on-resumed for a volume ranged TOC, with unit test * brailleapps#4: Added unit test for multiple volume breaks * brailleapps#4: Added class VolumeData for storage of a volume number and the atStartOfVolumeContents indication * brailleapps#4: Use dotify.api version 5.0.2 * brailleapps#4: Simplification of method TocSequenceEventImpl.rangeToVolume
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, if a manual break is inserted at some point to account for a single undesired volume break, volume breaks before the inserted manual break are also affected.
In combination with both manual volume breaks and manual editing, the current calculation might appear confusing to an editor. In this case, it would be more user friendly to set a target volume size (which isn't affected by the number of sheets to distribute), so that breaks preceding an inserted manual break remain in the same place as before. In other words, the value of this property would be used instead of the automatic target calculated based on the total number of sheets.
Example
If sheetCount is 120 and splitterMax is 50, the resulting volume sizes are (40, 40, 40). When introducing a break at sheet #90, the resulting sizes would be (45, 45, 30).
If a user doesn't want a manual break to affect breaks before the manual break, the splitterTarget property could be used. Setting splitterTarget to 40 would produce the volume sizes (40, 40, 10, 30) in this example.
The text was updated successfully, but these errors were encountered: