| Sunday, 21 March 2010 |
| Home · Downloads · Forum · Site Map · Support |
Slur bug with Version 2.0 Public Preview 1p | !327 |
Please note that you can see and participate in the most current discussion for this topic in our new user community area
- http://my.noteworthysoftware.com/?topic=5069 -
- http://my.noteworthysoftware.com/?topic=5069 -
| Started by marco on 2005-07-15 10:14:03 | |
Hello, last week I have updated to version 2.0 1p and strange inexistent slurs start appearing into some of my previous scores: they are shown for all the staff length as it appears on the screen (if you zoom out, slur will extend to the new measures now displayed because of the zoom action, even in those measures that was previously correctly displayed, up to the beginning of the staff). Sometimes these slurs are just a visual nuisance and they are not shown on the printed score, some other times they do result also in the printed pages. I could not sort out a rule to establish which notes/symbols combination produces this weird behaviour. I can send a file on request. marco | |
| Reply 1 by Lawrie Pardy on 2005-07-15 10:46:41 | |
Hi Marco, my guess is that you may have some hanging note ties to resolve. 1p handles ties differently in order to have more correct behaviour with notes with accidentals being tied over bar lines. (10 minute wait) There's a discussion about methods of finding hanging ties somewhere but I've been unable to find it, sorry. | |
| Reply 2 by Rick G. on 2005-07-15 17:08:51 | |
I saw a few of these using 1p. F9 seemed to fix it. There are lots more problems with 1p; best advice is to use 1m. | |
| Reply 3 by NoteWorthy Online on 2005-07-15 19:26:58 | |
Using any earlier preview before the latest preview is not recommended. Feel free to e-mail an example to support. We can review it and e-mail our impressions back to you. | |
| Reply 4 by G.. on 2005-07-18 07:43:08 | |
I had that problem but then I fixed it with 1q. | |
| Reply 5 by marco on 2005-07-18 08:13:48 | |
I have just installed 1q and everything is OK now. Thanks to Noteworthy staff for having solved the problem. | |