Auto multi-pageing

Bug #527514 reported by Bedlore
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
lyricue
Confirmed
Wishlist
Unassigned

Bug Description

While setting up our system it occurred to me that it may be beneficial if Lyricue was able to automatically break songs into multiple pages on request.

Long winded explanation follows. I follow the train of thought that less people intervention to run a system the better. I don't like to see a person become the "sound person" where it can be avoided, so when we can I prefer not to see someone having to manually change to new versus/chorus' of a song. Our little group of 20 or so generally meet in a home so even with longer songs projecting it as a single page is usually best as the smaller font will still be comfortable to read. However we occasionally join with other groups in a medium size hall in this situation the font size will be too small to be read from the greater distance, therefore the solution is to have the song broken into multiple pages so that the font size can be increased. However to do this currently in Lyricue we would have to maintain two versions of each song. It occurred to me that it might be possible to have a setting in Lyricue that when enabled automatically breaks the song into pages. It could simply look for an empty line to use as the break point or a special character could be used to give optimum control. (obviously the special character should not be projected). I guess it might also requre additional font size settings, ie. multi-page font size and single page font size.

Changed in lyricue:
importance: Undecided → Wishlist
Changed in lyricue:
status: New → Confirmed
Revision history for this message
Bedlore (brendan-dbinformatics) wrote :

Thanks Chris. I've been using the 'next verse' button now since you've told me about it but I still think this feature would be useful alternative. Sometimes its nice to present all scriptures been read in one hit, also I find the speed of the 'show next verse' function to be a hindrance although I've not re-tested in the latest csv version yet but versus pulled from the database were slow on my netbook and versus pulled from esword were practically unusable as you couldn't time it right, ie click the next verse around 6 seconds before its needed.

This isn't a high priority though.

klap-in (klap-in)
tags: added: featurerequest
removed: feature request
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.