I think that if the user does not have Braille support they should not be offered anything having to do with Braille. This would only create confusion. However, they might see a message box telling them to install Braille support. John On Thu, Jul 26, 2012 at 02:26:59AM +0100, Michael Whapples wrote: > I agree with what you say, therefore should we go further and say that > the user should never be offered a choice of one option? > > If the user has not got Braille support then should the dialog for > offering saving text or text and Braille be presented as they only have > one option to choose from? > > Michael Whapples > On 26/07/2012 02:23, John J. Boyer wrote: > >Translation and anything associated with it should be disabled if > >Braille support is not available. My intention was that if you didn't > >have Braille support you could still edit in the Daisy view. > > > >John > > > >On Thu, Jul 26, 2012 at 12:51:59AM +0100, Michael Whapples wrote: > >>OK, I notice something else which lead to me having a different > >>conclusion. > >> > >>If one does not have Braille support enabled (I hadn't got liblouisutdml > >>set up properly) then the text only radiobutton is selected by default, > >>but once I had Braille support working no radiobutton has focus by > >>default when both are available. This meant that at the beginning it > >>appeared like I could gain access in one direction. > >> > >>However, adding a group does improve matters a bit, it means access can > >>be achieved in one direction (like with the checkboxes). > >> > >>Michael Whapples > >>On 26/07/2012 00:43, Vic Beckley wrote: > >>>Michael, > >>> > >>>There was a problem when using checkboxes too. As long as you were in the > >>>controls it worked fine. As soon as you would tab or shift-tab past the > >>>last > >>>control you would be in this limbo land and tabbing would do nothing. You > >>>were probably in this shell object you describe. The radio buttons are > >>>not > >>>the entire problem. > >>> > >>> > >>>Best regards from Ohio, U.S.A., > >>> > >>>Vic > >>>E-mail: vic.beckley3@xxxxxxxxx > >>> > >>>-----Original Message----- > >>>From: brailleblaster-bounce@xxxxxxxxxxxxx > >>>[mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of Michael > >>>Whapples > >>>Sent: Wednesday, July 25, 2012 7:18 PM > >>>To: brailleblaster@xxxxxxxxxxxxx > >>>Subject: [brailleblaster] The problems with the save settings dialog > >>> > >>>Hello, > >>>The problem with selecting the radiobuttons for to save text or text and > >>>Braille, it appears what the problem is that between the "Cancel" button > >>>and the radiobuttons pressing tab or shift tab will take focus to the > >>>shell object and then the focus will not move anywhere by using > >>>tab/shift tab. > >>> > >>>I have looked at trying to set the tab order, this doesn't work, > >>>essentially one gets the problem where the tab order cycles round. > >>> > >>>Not quite sure why this happens when using radiobuttons but not > >>>checkboxes. I have tried using Group objects to group radiobuttons, but > >>>this does not solve the issue. > >>> > >>>While I am at it though, I noticed that the dialog does not have a shell > >>>as its parent, I would have expected the document window to be its > >>>parent. > >>> > >>>Also, may be this should be a proper dialog, you may want to read the > >>>Dialog javadoc for SWT which shows creating custom dialogs (IE. one > >>>which works in the way like the FileDialog provided by SWT, where it > >>>will give you a result when calling open() to show the dialog). > >>> > >>>Here is a link to the Dialog javadoc from SWT, > >>>http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.platform.doc.i > >>>sv%2Freference%2Fapi%2Forg%2Feclipse%2Fswt%2Fwidgets%2Fpackage-summary.html > >>> > >>>Michael Whapples > >>> > >>> > -- John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. http://www.abilitiessoft.com Madison, Wisconsin USA Developing software for people with disabilities