Zionworx feedback - bug list...
Posted: Mon Dec 19, 2005 11:37 am
I upgraded from Zionworx 2.0 to 2.5 on Tuesday and we ran it for the first time on Sunday. There was some wailing and gnashing of teeth so I thought I'd list the bugs we found.
1. Shared files
The first thing seems to be that the database in 2.5 isn't shared amongst all the Windows XP users. Our church PC has an admin account which has administrator rights and a set of normal user accounts. Zionworx 2.0 could be run by any user on the system, but 2.5 cannot find its database.
I'm assuming that this was a side effect of zionworx 2.0 putting its database directly under "Program Files/Zionworx" and windows automatically allows those files to be shared. Perhaps 2.5 could allow the database and settings files to be shared amongst all the Windows XP users. I got around the problem by enabling shared access to the database folder.
Related to this is the start menu items which need to go into "all users" rather than just the user that did the install, otherwise zionworx doesn't appear in the start menu. A quick manual copy fixed that one.
2. SLOW!!!!!
Wow! was 2.5 slow! A small mistake on one hymn meant that our words operator tried to fade out the song, change to to the right one and fade back in. We'd done two verses of the hymn before he got the words on the screen!
There seems to be a massive slowdown when fading songs which have images. 2.0 could fade in 128 steps in around 2 seconds, 2.5 is more like 20 seconds. There's no problem with the speed when there isn't an image on screen.
We also noticed that each hit on the space key would take 2 tenths of a second to respond when an image was onscreen but was instantaneous when using a colour background.
We've disabled fading for now but there's a general feeling that fading is important and they aren't happy about the delay in changing the words.
3. Widow and Orphan control
For some reason Zionworx splits a line across 2 screens. That doesn't seem sensible as it means the operator has to be really on the ball in hitting the space key so that people can see the rest of the line. Coupled with the slow response in 2.5 this caused a few hiccups on Sunday.
It would be nice if there was a "split lines across screens?" option as part of the style
4. What's with the "[Default]" styles?
We've got around 20 "[Default]" styles listed which we didn't create. How do we get rid of them? They were just there after the upgrade.
5. Changing style stops next screen
If you change the style of a song then the "next screen" display disapears from the right hand pane and you need 2 hits on the space key to bring it up. This caught out the operator a couple of times as he set the style, then brought up the display and didn't realise that the next screen wasn't ready.
6. Song scrolling jumps
The song display on the right doesn't scroll properly. It seems to jump to screen boundaries which makes it difficult to proof read a song when the display keeps leaping 8 lines at a time. Scrolling should be smooth.
7. Assigning default style doesn't re-layout the song
If you change the text style in a song to something quite small and then use the little icon to return to the default style then the song isn't laid out again and the display is messed up. Double clicking the song in the playlist corrects the problem.
1. Shared files
The first thing seems to be that the database in 2.5 isn't shared amongst all the Windows XP users. Our church PC has an admin account which has administrator rights and a set of normal user accounts. Zionworx 2.0 could be run by any user on the system, but 2.5 cannot find its database.
I'm assuming that this was a side effect of zionworx 2.0 putting its database directly under "Program Files/Zionworx" and windows automatically allows those files to be shared. Perhaps 2.5 could allow the database and settings files to be shared amongst all the Windows XP users. I got around the problem by enabling shared access to the database folder.
Related to this is the start menu items which need to go into "all users" rather than just the user that did the install, otherwise zionworx doesn't appear in the start menu. A quick manual copy fixed that one.
2. SLOW!!!!!
Wow! was 2.5 slow! A small mistake on one hymn meant that our words operator tried to fade out the song, change to to the right one and fade back in. We'd done two verses of the hymn before he got the words on the screen!
There seems to be a massive slowdown when fading songs which have images. 2.0 could fade in 128 steps in around 2 seconds, 2.5 is more like 20 seconds. There's no problem with the speed when there isn't an image on screen.
We also noticed that each hit on the space key would take 2 tenths of a second to respond when an image was onscreen but was instantaneous when using a colour background.
We've disabled fading for now but there's a general feeling that fading is important and they aren't happy about the delay in changing the words.
3. Widow and Orphan control
For some reason Zionworx splits a line across 2 screens. That doesn't seem sensible as it means the operator has to be really on the ball in hitting the space key so that people can see the rest of the line. Coupled with the slow response in 2.5 this caused a few hiccups on Sunday.
It would be nice if there was a "split lines across screens?" option as part of the style
4. What's with the "[Default]" styles?
We've got around 20 "[Default]" styles listed which we didn't create. How do we get rid of them? They were just there after the upgrade.
5. Changing style stops next screen
If you change the style of a song then the "next screen" display disapears from the right hand pane and you need 2 hits on the space key to bring it up. This caught out the operator a couple of times as he set the style, then brought up the display and didn't realise that the next screen wasn't ready.
6. Song scrolling jumps
The song display on the right doesn't scroll properly. It seems to jump to screen boundaries which makes it difficult to proof read a song when the display keeps leaping 8 lines at a time. Scrolling should be smooth.
7. Assigning default style doesn't re-layout the song
If you change the text style in a song to something quite small and then use the little icon to return to the default style then the song isn't laid out again and the display is messed up. Double clicking the song in the playlist corrects the problem.