Ramy, We have a plan for improving the navigation and content of the documentation, but the initial objective is to get the code stable and it's not possible to embark on a large documentation effort until we've achieved that primary goal. It would be a waste of scarce time to write documentation, find we need to change the code to address an issue, then have to write the documentation again, so please bear with us - this is Version 1, beta 1, after all. Best wishes. Tim Burgess Raised Bar Ltd Phone: +44 (0)1827 719822 Don't forget to vote for improved access to music and music technology at http://www.raisedbar.net/petition.htm -----Original Message----- From: sib-access-bounce@xxxxxxxxxxxxx [mailto:sib-access-bounce@xxxxxxxxxxxxx] On Behalf Of Ramy Moustafa Sent: 09 October 2008 14:43 To: sib-access@xxxxxxxxxxxxx Subject: [sib-access] Re: Confusing Section of Milestone.doc dann: I saw in sibelius speaking the our help docs r divided to chapters,. Can't we make this? i mean, put each chapter in 1 file, to be easier to navigate and to get anyinfo that i need while working? Thanks Cheers Ramy MOustafa ----- Original Message ----- From: "Dan Rugman" <sib-access@xxxxxxxxxxxxxxxxx> To: <sib-access@xxxxxxxxxxxxx> Sent: Monday, October 06, 2008 11:49 AM Subject: [sib-access] Re: Confusing Section of Milestone.doc > Dave, there's a newer version of the milestone 1 doc on the website > which has a corrected version of this passage. I've copied it below > but you might > want to download the newer doc anyway. > > > The input devices page of this dialog causes JAWS some problems. > Unfortunately, the name of the device in the list of devices is not > spoken because JAWS causes the text to literally disappear from the screen. > However, there is a way to determine which device is selected by using > the "test MIDI" option in the Sibelius Access menu. Full details are > given in the guide (Input Devices), but the steps can be briefly > summarised as > follows: > > Ensure that all items are activated. > Select the device you need to identify. > Diactivate it. > Start testing MIDI. > Play each MIDI device in turn. > The one which doesn't get a response will be the one deactivated in > the list. > > Dan Rugman > > Visit www.musicaccess.co.uk > The new on-line resource for visually impaired musicians and home of > Sibelius Access. > > -----Original Message----- > From: sib-access-bounce@xxxxxxxxxxxxx > [mailto:sib-access-bounce@xxxxxxxxxxxxx] On Behalf Of Dave 'SqueezeBox' > Carlson > Sent: 06 October 2008 16:51 > To: sib-access@xxxxxxxxxxxxx > Subject: [sib-access] Confusing Section of Milestone.doc > > Dan and Tim, > > This section, under "Preferences" is confusing. Can you clear it up? > > The input devices page of this dialog causes JAWS some problems. > Unfortunately, > the name of the device in the list of devices is not spoken because > JAWS causes the text to literally disappear from the screen. However, > there is a > way to determine which device is selected by using the "test MIDI" > option in > the Speak the keystroke when moving through the lists of existing shortcuts. > Prevent the tab and shift Tab keys from being trapped in add keystroke > fields. > > > Dave > > If you wish to unsubscribe, send a blank message with the single word, > unsubscribe - in the Subject line to: > sib-access-request@xxxxxxxxxxxxx > > > If you wish to unsubscribe, send a blank message with the single word, > unsubscribe - in the Subject line to: > sib-access-request@xxxxxxxxxxxxx If you wish to unsubscribe, send a blank message with the single word, unsubscribe - in the Subject line to: sib-access-request@xxxxxxxxxxxxx If you wish to unsubscribe, send a blank message with the single word, unsubscribe - in the Subject line to: sib-access-request@xxxxxxxxxxxxx