View Single Post
Old 10-19-2010, 10:19 AM   #113
badbob001
Fanatic
badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.badbob001 ought to be getting tired of karma fortunes by now.
 
badbob001's Avatar
 
Posts: 556
Karma: 1102020
Join Date: Sep 2009
Device: Kindle Keyboard (rip), Kindle Voyage, Fire Tablet 10 '17, iPad '19
Ok, but I just didn't want an arbitrary auto_split_buffer percentage to push the final image beyond the target dimensions. It would be nicer if the overlap buffer was dynamically determined based on how much leftover space there will be after the split.

Say the target device is 600x800 and there is a 1000x800 page. A non-buffered split would be 2 x 500x800 pages. With bordering, it'll add 50 pixels to the left/right sides of each page. It would look better to only add the border to the sides away from dividing edge:
[border][left page] [right page][border]
Now it is very clear visually which side of each page is the divider.

Another idea would be a dynamic overlap buffer that would calculate how much room is left (600-1000/2=100) and add that difference to to the left and right pages so we don't have to deal with borders for splits.
[left page][100 pixel overlap] [pixel overlap][right page]

Just some suggestions. App is still awesome.
badbob001 is offline   Reply With Quote