openlp-core team mailing list archive

[Azaziah <suutari.olli@xxxxxxxxx>]

My understanding of a "Force split" (which I get from OPS Pro) would be a new a new tag (perhaps "[===]") that would force a verse to be split into 2 (or more) slides when presenting. This would keep the verse in one "frame"/verse in the editor, but would be 2 slides when presenting.

Thank you for your comment.
I agree, this would be a better solution.
I especially like the idea of having the verse staying as a single verse in the editor.

However, this is harder to execute than the suggested solution.
Conversion of the Optional split tags happens in render.py

It’s already a fairly complex process, and I’m not sure if I have enough 
programming skills to make it work for checking both tags.

Basically OLP should first check for force split tags and then force 
the split based on given position. (This would require some new functions),
after that the checking for optional splits should be done.

One thing I would love to see OpenLP doing in the future is scaling font sizes.

The basic idea would be: If text does not fit 1 slide
and font size is smaller than the minimum font size, 
try reducing the size until text fits or min font size
is reached, if text still does not fit the slide, do 
the optional split/automatic split on last fitting row.

If we were to add 2nd “Split tag”, we would have to do
the conversion in renderer, this could potentially cause
some trouble with the scaling fonts but should not be a
problem assuming the font size is checked after the force
split tags.

Here’s some code from the renderer.py
https://gist.github.com/anonymous/398f1864a3fbfa3114d34a10ee73b0ce

The upside of the currently suggested solution is the fact it does
not require any additional functions for renderer.py it’s true that
it’s already possible to do the “Force split” by using the insert 
button, but this requires:

1. Selecting the proper verse tag for the verse you want to split
2. Selecting the proper number for the verse you want to split 
   (It automatically adds +1 to the current verse number).
3. Clicking the insert button.
4. Removing the new unrequired empty line created by the insert function
5. Knowing it’s possible to split verses like this.

The suggested solution does this all when the “Split” button is pressed.
Overflow Split could be more describing, but perhaps not so easy to 
understand for the people with lesser English skills.

Users would probably still get confused by it, I believe having the “Split”
button available would end this problem.

It would probably be best if we did both of these things.
-- 
https://code.launchpad.net/~suutari-olli/openlp/force-split/+merge/296002
Your team OpenLP Core is subscribed to branch lp:openlp.