0.9.29: Notes on different areas
Hi Harri! Here are a few notes/observations I have collected since 0.9.28 and 0.9.29. Hope some of this is useful. Textbuffer When text buffer is activated for the first time: Focus is not moved to the text field, but stays on the unlabeled button which closes the text buffer I have to swipe to the text field to make sure focus is in the right place. This is especially important for Braille display users since they aren't sure that the cursor is vissible on the screen, so they have to make a few gestures/keypresses to be able to entering Braille into the field and follow their typing. goto command can not find apps on device. I have an app on my device named: Smartthings from Samsung. If I type: goto smartthings followed by a newline, MBraille returns app not found. Why can't MBraille find the app, if it doesn't look in a premade list of apps? This is true for both braille editor and external keyboard mode. Text buffer: Audio ducking is not suspended As noticed in another thread about audio ducking I found a workaround for this behaviour. This is however not working when using external keyboard mode. Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor. Request: Can apps like Todoist be supported in a future version? Todoist should have a good acccessibility rank both on iOS and Android. I use Todoist for almost anything, I have started to make notes for MBraille observations as of lately. I have ben in contact with their support, and they are really interested in accessibility, also if they by accident breaks something. Editor: Promp for saving if a file is open This was drawn to my attention, when I looked for adding aliases to alias.mb I opened the alias.mb via the open command. I entered a few lines, and wanted to close the file. MBraille closed the file and my edits were lost. I wonder if a check can be made, so MBraille will Promt: Save changes to "filename"? Yes, no? Future feature request: Command to switch between keyboard modes This might almost never be used, but I would really like for a setting that allows me to switch between braille input on screen and external keyboard mode. Muy first thought was trying to make MBraille smart enough, so it would switch mode if it detected input from an external device, but I think that is almost impossible to program. Text buffer: The label/help text for the edit field is repeated when reading the text. It would be fine, if the text for the edit field itself was: Type text here. Notes on generated help file: There are a few places where formatting is escaped. For example under the paragraph: Multiple lines in aliases There is a list, but the blank line before the 1. is missing (I guess), and therefor the list is treated as regular text. Hope some of this is useful. Best regards Thomas Sendt fra min Macbook Pro via Apple mail
Hi Thomas, I'm going through your feedback below. The following I did not quite grasp: Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor. What do you mean? Any text in the editor should be passed to the command as usual. Best regards, Harri On Wednesday, April 15th, 2026 at 11:16 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote:
Hi Harri!
Here are a few notes/observations I have collected since 0.9.28 and 0.9.29. Hope some of this is useful. Textbuffer
When text buffer is activated for the first time: Focus is not moved to the text field, but stays on the unlabeled button which closes the text buffer I have to swipe to the text field to make sure focus is in the right place. This is especially important for Braille display users since they aren't sure that the cursor is vissible on the screen, so they have to make a few gestures/keypresses to be able to entering Braille into the field and follow their typing.
goto command can not find apps on device. I have an app on my device named: Smartthings from Samsung. If I type: goto smartthings followed by a newline, MBraille returns app not found. Why can't MBraille find the app, if it doesn't look in a premade list of apps? This is true for both braille editor and external keyboard mode.
Text buffer: Audio ducking is not suspended
As noticed in another thread about audio ducking I found a workaround for this behaviour. This is however not working when using external keyboard mode.
Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor.
Request: Can apps like Todoist be supported in a future version? Todoist should have a good acccessibility rank both on iOS and Android. I use Todoist for almost anything, I have started to make notes for MBraille observations as of lately. I have ben in contact with their support, and they are really interested in accessibility, also if they by accident breaks something.
Editor: Promp for saving if a file is open This was drawn to my attention, when I looked for adding aliases to alias.mb I opened the alias.mb via the open command. I entered a few lines, and wanted to close the file. MBraille closed the file and my edits were lost. I wonder if a check can be made, so MBraille will Promt: Save changes to "filename"? Yes, no?
Future feature request: Command to switch between keyboard modes This might almost never be used, but I would really like for a setting that allows me to switch between braille input on screen and external keyboard mode. Muy first thought was trying to make MBraille smart enough, so it would switch mode if it detected input from an external device, but I think that is almost impossible to program.
Text buffer: The label/help text for the edit field is repeated when reading the text. It would be fine, if the text for the edit field itself was: Type text here.
Notes on generated help file:
There are a few places where formatting is escaped. For example under the paragraph: Multiple lines in aliases There is a list, but the blank line before the 1. is missing (I guess), and therefor the list is treated as regular text.
Hope some of this is useful.
Best regards Thomas
Sendt fra min Macbook Pro via Apple mail
Hi Harri! Sorry if I was unclear about that part. Is it a feature or a bug that holding down dot 4 and swiping up/down will move through the command history? From what I read in the help the history should only work inside the command mode. If this is a feature, I really like that, and it gives MBraille a blast from the past. :) I only thought the command history was possible to navigate through when command mode was activated first. Best regards Thomas Sendt fra min Macbook Pro via Apple mail
Den 17. apr. 2026 kl. 21.02 skrev Harri Pasanen via MBraille-Test <mbraille-test@lists.mpaja.com>:
Hi Thomas,
I'm going through your feedback below. The following I did not quite grasp:
Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor.
What do you mean? Any text in the editor should be passed to the command as usual.
Best regards, Harri
On Wednesday, April 15th, 2026 at 11:16 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote:
Hi Harri!
Here are a few notes/observations I have collected since 0.9.28 and 0.9.29. Hope some of this is useful. Textbuffer
When text buffer is activated for the first time: Focus is not moved to the text field, but stays on the unlabeled button which closes the text buffer I have to swipe to the text field to make sure focus is in the right place. This is especially important for Braille display users since they aren't sure that the cursor is vissible on the screen, so they have to make a few gestures/keypresses to be able to entering Braille into the field and follow their typing.
goto command can not find apps on device. I have an app on my device named: Smartthings from Samsung. If I type: goto smartthings followed by a newline, MBraille returns app not found. Why can't MBraille find the app, if it doesn't look in a premade list of apps? This is true for both braille editor and external keyboard mode.
Text buffer: Audio ducking is not suspended
As noticed in another thread about audio ducking I found a workaround for this behaviour. This is however not working when using external keyboard mode.
Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor.
Request: Can apps like Todoist be supported in a future version? Todoist should have a good acccessibility rank both on iOS and Android. I use Todoist for almost anything, I have started to make notes for MBraille observations as of lately. I have ben in contact with their support, and they are really interested in accessibility, also if they by accident breaks something.
Editor: Promp for saving if a file is open This was drawn to my attention, when I looked for adding aliases to alias.mb I opened the alias.mb via the open command. I entered a few lines, and wanted to close the file. MBraille closed the file and my edits were lost. I wonder if a check can be made, so MBraille will Promt: Save changes to "filename"? Yes, no?
Future feature request: Command to switch between keyboard modes This might almost never be used, but I would really like for a setting that allows me to switch between braille input on screen and external keyboard mode. Muy first thought was trying to make MBraille smart enough, so it would switch mode if it detected input from an external device, but I think that is almost impossible to program.
Text buffer: The label/help text for the edit field is repeated when reading the text. It would be fine, if the text for the edit field itself was: Type text here.
Notes on generated help file:
There are a few places where formatting is escaped. For example under the paragraph: Multiple lines in aliases There is a list, but the blank line before the 1. is missing (I guess), and therefor the list is treated as regular text.
Hope some of this is useful.
Best regards Thomas
Sendt fra min Macbook Pro via Apple mail
_______________________________________________ MBraille-Test mailing list -- mbraille-test@lists.mpaja.com To unsubscribe send an email to mbraille-test-leave@lists.mpaja.com
Hi, It is a feature, the command mode is implicitly activated with holding dot 4 and swiping up or down to browse command history. So no need to got to command mode first. Best regards, Harri On Friday, April 17th, 2026 at 10:09 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote:
Hi Harri!
Sorry if I was unclear about that part. Is it a feature or a bug that holding down dot 4 and swiping up/down will move through the command history? From what I read in the help the history should only work inside the command mode. If this is a feature, I really like that, and it gives MBraille a blast from the past. :) I only thought the command history was possible to navigate through when command mode was activated first.
Best regards Thomas
Sendt fra min Macbook Pro via Apple mail
Den 17. apr. 2026 kl. 21.02 skrev Harri Pasanen via MBraille-Test <mbraille-test@lists.mpaja.com>:
Hi Thomas,
I'm going through your feedback below. The following I did not quite grasp:
Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor.
What do you mean? Any text in the editor should be passed to the command as usual.
Best regards, Harri
On Wednesday, April 15th, 2026 at 11:16 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote:
Hi Harri!
Here are a few notes/observations I have collected since 0.9.28 and 0.9.29. Hope some of this is useful. Textbuffer
When text buffer is activated for the first time: Focus is not moved to the text field, but stays on the unlabeled button which closes the text buffer I have to swipe to the text field to make sure focus is in the right place. This is especially important for Braille display users since they aren't sure that the cursor is vissible on the screen, so they have to make a few gestures/keypresses to be able to entering Braille into the field and follow their typing.
goto command can not find apps on device. I have an app on my device named: Smartthings from Samsung. If I type: goto smartthings followed by a newline, MBraille returns app not found. Why can't MBraille find the app, if it doesn't look in a premade list of apps? This is true for both braille editor and external keyboard mode.
Text buffer: Audio ducking is not suspended
As noticed in another thread about audio ducking I found a workaround for this behaviour. This is however not working when using external keyboard mode.
Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor.
Request: Can apps like Todoist be supported in a future version? Todoist should have a good acccessibility rank both on iOS and Android. I use Todoist for almost anything, I have started to make notes for MBraille observations as of lately. I have ben in contact with their support, and they are really interested in accessibility, also if they by accident breaks something.
Editor: Promp for saving if a file is open This was drawn to my attention, when I looked for adding aliases to alias.mb I opened the alias.mb via the open command. I entered a few lines, and wanted to close the file. MBraille closed the file and my edits were lost. I wonder if a check can be made, so MBraille will Promt: Save changes to "filename"? Yes, no?
Future feature request: Command to switch between keyboard modes This might almost never be used, but I would really like for a setting that allows me to switch between braille input on screen and external keyboard mode. Muy first thought was trying to make MBraille smart enough, so it would switch mode if it detected input from an external device, but I think that is almost impossible to program.
Text buffer: The label/help text for the edit field is repeated when reading the text. It would be fine, if the text for the edit field itself was: Type text here.
Notes on generated help file:
There are a few places where formatting is escaped. For example under the paragraph: Multiple lines in aliases There is a list, but the blank line before the 1. is missing (I guess), and therefor the list is treated as regular text.
Hope some of this is useful.
Best regards Thomas
Sendt fra min Macbook Pro via Apple mail
_______________________________________________ MBraille-Test mailing list -- mbraille-test@lists.mpaja.com To unsubscribe send an email to mbraille-test-leave@lists.mpaja.com
That is very powerful and useful. My only concern is when gestures get triggered by accident and one is not aware that you’re issuing a command or, as I reported in separate feedback, sometimes one ends up in command mode without sound indication by accident and it can be confusing. Best, Ioana Ioana Gandrabur Peer trainer / Paire Formatrice Ioana.gandrabur@celalibrary.ca<mailto:Ioana.gandrabur@celalibrary.ca> 437 291-4095 www.celalibrary.ca<http://www.celalibrary.ca/> www.bibliocaeb.ca<http://www.bibliocaeb.ca/> I respectfully acknowledge that I live and work on the traditional, unceded lands of the Kanien’kehá:ka (Mohawk) Nation — a historic gathering place for many First Peoples, including the Haudenosaunee, Anishinaabeg, Huron-Wendat, and others. Je reconnais respectueusement que je vis et travaille sur les terres traditionnelles non cédées de la nation kanien’kehá:ka (mohawk) — un lieu de rencontre historique pour de nombreux peuples autochtones, Anishinaabeg, les Hurons-Wendat et d’autres. From: Harri Pasanen via MBraille-Test <mbraille-test@lists.mpaja.com> Sent: Friday, April 17, 2026 3:58 PM To: This list is for MBraille testers. You will get access to beta versions and latest features still in development. <mbraille-test@lists.mpaja.com> Cc: Harri Pasanen <harri@mpaja.com> Subject: [MBraille-Test] Re: 0.9.29: Notes on different areas Hi, It is a feature, the command mode is implicitly activated with holding dot 4 and swiping up or down to browse command history. So no need to got to command mode first. Best regards, Harri On Friday, April 17th, 2026 at 10:09 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote: Hi Harri! Sorry if I was unclear about that part. Is it a feature or a bug that holding down dot 4 and swiping up/down will move through the command history? From what I read in the help the history should only work inside the command mode. If this is a feature, I really like that, and it gives MBraille a blast from the past. :) I only thought the command history was possible to navigate through when command mode was activated first. Best regards Thomas Sendt fra min Macbook Pro via Apple mail Den 17. apr. 2026 kl. 21.02 skrev Harri Pasanen via MBraille-Test <mbraille-test@lists.mpaja.com>: Hi Thomas, I'm going through your feedback below. The following I did not quite grasp: Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor. What do you mean? Any text in the editor should be passed to the command as usual. Best regards, Harri On Wednesday, April 15th, 2026 at 11:16 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote: Hi Harri! Here are a few notes/observations I have collected since 0.9.28 and 0.9.29. Hope some of this is useful. Textbuffer When text buffer is activated for the first time: Focus is not moved to the text field, but stays on the unlabeled button which closes the text buffer I have to swipe to the text field to make sure focus is in the right place. This is especially important for Braille display users since they aren't sure that the cursor is vissible on the screen, so they have to make a few gestures/keypresses to be able to entering Braille into the field and follow their typing. goto command can not find apps on device. I have an app on my device named: Smartthings from Samsung. If I type: goto smartthings followed by a newline, MBraille returns app not found. Why can't MBraille find the app, if it doesn't look in a premade list of apps? This is true for both braille editor and external keyboard mode. Text buffer: Audio ducking is not suspended As noticed in another thread about audio ducking I found a workaround for this behaviour. This is however not working when using external keyboard mode. Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor. Request: Can apps like Todoist be supported in a future version? Todoist should have a good acccessibility rank both on iOS and Android. I use Todoist for almost anything, I have started to make notes for MBraille observations as of lately. I have ben in contact with their support, and they are really interested in accessibility, also if they by accident breaks something. Editor: Promp for saving if a file is open This was drawn to my attention, when I looked for adding aliases to alias.mb I opened the alias.mb via the open command. I entered a few lines, and wanted to close the file. MBraille closed the file and my edits were lost. I wonder if a check can be made, so MBraille will Promt: Save changes to "filename"? Yes, no? Future feature request: Command to switch between keyboard modes This might almost never be used, but I would really like for a setting that allows me to switch between braille input on screen and external keyboard mode. Muy first thought was trying to make MBraille smart enough, so it would switch mode if it detected input from an external device, but I think that is almost impossible to program. Text buffer: The label/help text for the edit field is repeated when reading the text. It would be fine, if the text for the edit field itself was: Type text here. Notes on generated help file: There are a few places where formatting is escaped. For example under the paragraph: Multiple lines in aliases There is a list, but the blank line before the 1. is missing (I guess), and therefor the list is treated as regular text. Hope some of this is useful. Best regards Thomas Sendt fra min Macbook Pro via Apple mail _______________________________________________ MBraille-Test mailing list -- mbraille-test@lists.mpaja.com To unsubscribe send an email to mbraille-test-leave@lists.mpaja.com Privacy Disclaimer - Français à suivre This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary, and confidential. If you are not the intended recipient, you are notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately. ----------------------------------------------------------------------------------- Déclaration de confidentialité Le présent courrier électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. Si ce message vous a été transmis par erreur, veuillez en informer l'expéditeur et le supprimer immédiatement.
Hi, I'm wondering what would be the best way to address this. - have a longer audio beep / effect when transferring to command mode, or different user selectable beeps. - have maybe two vibrations to indicate it - change the gesture for command mode, or have it configurable, similar to way undo gesture is configurable in the settings. Any opinions? Best regards, Harri On Friday, April 17th, 2026 at 11:33 PM, Ioana Gandrabur via MBraille-Test <mbraille-test@lists.mpaja.com> wrote:
[That is very powerful and useful.]
My only concern is when gestures get triggered by accident and one is not aware that you’re issuing a command or, as I reported in separate feedback, sometimes one ends up in command mode without sound indication by accident and it can be confusing.
Best,
Ioana
Ioana Gandrabur
Peer trainer / Paire Formatrice
Ioana.gandrabur@celalibrary.ca
437 291-4095
[www.celalibrary.ca](http://www.celalibrary.ca/)
[www.bibliocaeb.ca](http://www.bibliocaeb.ca/)
I respectfully acknowledge that I live and work on the traditional, unceded lands of the Kanien’kehá:ka (Mohawk) Nation — a historic gathering place for many First Peoples, including the Haudenosaunee, Anishinaabeg, Huron-Wendat, and others.
Je reconnais respectueusement que je vis et travaille sur les terres traditionnelles non cédées de la nation kanien’kehá:ka (mohawk) — un lieu de rencontre historique pour de nombreux peuples autochtones, Anishinaabeg, les Hurons-Wendat et d’autres.
From: Harri Pasanen via MBraille-Test <mbraille-test@lists.mpaja.com> Sent: Friday, April 17, 2026 3:58 PM To: This list is for MBraille testers. You will get access to beta versions and latest features still in development. <mbraille-test@lists.mpaja.com> Cc: Harri Pasanen <harri@mpaja.com> Subject: [MBraille-Test] Re: 0.9.29: Notes on different areas
Hi,
It is a feature, the command mode is implicitly activated with holding dot 4 and swiping up or down to browse command history. So no need to got to command mode first.
Best regards,
Harri
On Friday, April 17th, 2026 at 10:09 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote:
Hi Harri!
Sorry if I was unclear about that part.
Is it a feature or a bug that holding down dot 4 and swiping up/down will move through the command history?
From what I read in the help the history should only work inside the command mode. If this is a feature, I really like that, and it gives MBraille a blast from the past. :)
I only thought the command history was possible to navigate through when command mode was activated first.
Best regards Thomas
Sendt fra min Macbook Pro via Apple mail
Den 17. apr. 2026 kl. 21.02 skrev Harri Pasanen via MBraille-Test <mbraille-test@lists.mpaja.com>:
Hi Thomas,
I'm going through your feedback below. The following I did not quite grasp:
Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor.
What do you mean? Any text in the editor should be passed to the command as usual.
Best regards,
Harri
On Wednesday, April 15th, 2026 at 11:16 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote:
Hi Harri!
Here are a few notes/observations I have collected since 0.9.28 and 0.9.29. Hope some of this is useful. Textbuffer
When text buffer is activated for the first time: Focus is not moved to the text field, but stays on the unlabeled button which closes the text buffer I have to swipe to the text field to make sure focus is in the right place. This is especially important for Braille display users since they aren't sure that the cursor is vissible on the screen, so they have to make a few gestures/keypresses to be able to entering Braille into the field and follow their typing.
goto command can not find apps on device. I have an app on my device named: Smartthings from Samsung. If I type: goto smartthings followed by a newline, MBraille returns app not found. Why can't MBraille find the app, if it doesn't look in a premade list of apps? This is true for both braille editor and external keyboard mode.
Text buffer: Audio ducking is not suspended
As noticed in another thread about audio ducking I found a workaround for this behaviour. This is however not working when using external keyboard mode.
Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor.
Request: Can apps like Todoist be supported in a future version? Todoist should have a good acccessibility rank both on iOS and Android. I use Todoist for almost anything, I have started to make notes for MBraille observations as of lately. I have ben in contact with their support, and they are really interested in accessibility, also if they by accident breaks something.
Editor: Promp for saving if a file is open This was drawn to my attention, when I looked for adding aliases to alias.mb I opened the alias.mb via the open command. I entered a few lines, and wanted to close the file. MBraille closed the file and my edits were lost. I wonder if a check can be made, so MBraille will Promt: Save changes to "filename"? Yes, no?
Future feature request: Command to switch between keyboard modes This might almost never be used, but I would really like for a setting that allows me to switch between braille input on screen and external keyboard mode. Muy first thought was trying to make MBraille smart enough, so it would switch mode if it detected input from an external device, but I think that is almost impossible to program.
Text buffer: The label/help text for the edit field is repeated when reading the text. It would be fine, if the text for the edit field itself was: Type text here.
Notes on generated help file:
There are a few places where formatting is escaped. For example under the paragraph: Multiple lines in aliases There is a list, but the blank line before the 1. is missing (I guess), and therefor the list is treated as regular text.
Hope some of this is useful.
Best regards Thomas
Sendt fra min Macbook Pro via Apple mail
_______________________________________________ MBraille-Test mailing list -- mbraille-test@lists.mpaja.com To unsubscribe send an email to mbraille-test-leave@lists.mpaja.com
Privacy Disclaimer - Français à suivre This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary, and confidential. If you are not the intended recipient, you are notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately. ----------------------------------------------------------------------------------- Déclaration de confidentialité Le présent courrier électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. Si ce message vous a été transmis par erreur, veuillez en informer l'expéditeur et le supprimer immédiatement.
Hi, I like option 2 and 3, as long as vibration is different enough from spelling or those for typing if people have those turned on. Sent from my iPhone On Apr 19, 2026, at 8:51 AM, Harri Pasanen via MBraille-Test <mbraille-test@lists.mpaja.com> wrote: Hi, I'm wondering what would be the best way to address this. 1. have a longer audio beep / effect when transferring to command mode, or different user selectable beeps. 2. have maybe two vibrations to indicate it 3. change the gesture for command mode, or have it configurable, similar to way undo gesture is configurable in the settings. Any opinions? Best regards, Harri On Friday, April 17th, 2026 at 11:33 PM, Ioana Gandrabur via MBraille-Test <mbraille-test@lists.mpaja.com> wrote: That is very powerful and useful. My only concern is when gestures get triggered by accident and one is not aware that you’re issuing a command or, as I reported in separate feedback, sometimes one ends up in command mode without sound indication by accident and it can be confusing. Best, Ioana Ioana Gandrabur Peer trainer / Paire Formatrice Ioana.gandrabur@celalibrary.ca<mailto:Ioana.gandrabur@celalibrary.ca> 437 291-4095 www.celalibrary.ca<http://www.celalibrary.ca/> www.bibliocaeb.ca<http://www.bibliocaeb.ca/> I respectfully acknowledge that I live and work on the traditional, unceded lands of the Kanien’kehá:ka (Mohawk) Nation — a historic gathering place for many First Peoples, including the Haudenosaunee, Anishinaabeg, Huron-Wendat, and others. Je reconnais respectueusement que je vis et travaille sur les terres traditionnelles non cédées de la nation kanien’kehá:ka (mohawk) — un lieu de rencontre historique pour de nombreux peuples autochtones, Anishinaabeg, les Hurons-Wendat et d’autres. From: Harri Pasanen via MBraille-Test <mbraille-test@lists.mpaja.com> Sent: Friday, April 17, 2026 3:58 PM To: This list is for MBraille testers. You will get access to beta versions and latest features still in development. <mbraille-test@lists.mpaja.com> Cc: Harri Pasanen <harri@mpaja.com> Subject: [MBraille-Test] Re: 0.9.29: Notes on different areas Hi, It is a feature, the command mode is implicitly activated with holding dot 4 and swiping up or down to browse command history. So no need to got to command mode first. Best regards, Harri On Friday, April 17th, 2026 at 10:09 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote: Hi Harri! Sorry if I was unclear about that part. Is it a feature or a bug that holding down dot 4 and swiping up/down will move through the command history? From what I read in the help the history should only work inside the command mode. If this is a feature, I really like that, and it gives MBraille a blast from the past. :) I only thought the command history was possible to navigate through when command mode was activated first. Best regards Thomas Sendt fra min Macbook Pro via Apple mail Den 17. apr. 2026 kl. 21.02 skrev Harri Pasanen via MBraille-Test <mbraille-test@lists.mpaja.com>: Hi Thomas, I'm going through your feedback below. The following I did not quite grasp: Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor. What do you mean? Any text in the editor should be passed to the command as usual. Best regards, Harri On Wednesday, April 15th, 2026 at 11:16 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote: Hi Harri! Here are a few notes/observations I have collected since 0.9.28 and 0.9.29. Hope some of this is useful. Textbuffer When text buffer is activated for the first time: Focus is not moved to the text field, but stays on the unlabeled button which closes the text buffer I have to swipe to the text field to make sure focus is in the right place. This is especially important for Braille display users since they aren't sure that the cursor is vissible on the screen, so they have to make a few gestures/keypresses to be able to entering Braille into the field and follow their typing. goto command can not find apps on device. I have an app on my device named: Smartthings from Samsung. If I type: goto smartthings followed by a newline, MBraille returns app not found. Why can't MBraille find the app, if it doesn't look in a premade list of apps? This is true for both braille editor and external keyboard mode. Text buffer: Audio ducking is not suspended As noticed in another thread about audio ducking I found a workaround for this behaviour. This is however not working when using external keyboard mode. Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor. Request: Can apps like Todoist be supported in a future version? Todoist should have a good acccessibility rank both on iOS and Android. I use Todoist for almost anything, I have started to make notes for MBraille observations as of lately. I have ben in contact with their support, and they are really interested in accessibility, also if they by accident breaks something. Editor: Promp for saving if a file is open This was drawn to my attention, when I looked for adding aliases to alias.mb I opened the alias.mb via the open command. I entered a few lines, and wanted to close the file. MBraille closed the file and my edits were lost. I wonder if a check can be made, so MBraille will Promt: Save changes to "filename"? Yes, no? Future feature request: Command to switch between keyboard modes This might almost never be used, but I would really like for a setting that allows me to switch between braille input on screen and external keyboard mode. Muy first thought was trying to make MBraille smart enough, so it would switch mode if it detected input from an external device, but I think that is almost impossible to program. Text buffer: The label/help text for the edit field is repeated when reading the text. It would be fine, if the text for the edit field itself was: Type text here. Notes on generated help file: There are a few places where formatting is escaped. For example under the paragraph: Multiple lines in aliases There is a list, but the blank line before the 1. is missing (I guess), and therefor the list is treated as regular text. Hope some of this is useful. Best regards Thomas Sendt fra min Macbook Pro via Apple mail _______________________________________________ MBraille-Test mailing list -- mbraille-test@lists.mpaja.com To unsubscribe send an email to mbraille-test-leave@lists.mpaja.com Privacy Disclaimer - Français à suivre This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary, and confidential. If you are not the intended recipient, you are notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately. ----------------------------------------------------------------------------------- Déclaration de confidentialité Le présent courrier électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. Si ce message vous a été transmis par erreur, veuillez en informer l'expéditeur et le supprimer immédiatement. _______________________________________________ MBraille-Test mailing list -- mbraille-test@lists.mpaja.com To unsubscribe send an email to mbraille-test-leave@lists.mpaja.com
Hi Harri! I have only seen this issue due to dot 4 being hold down triggered by lag/swipe sensitivity. The three finger swipe up have never ben an issue for me. I would go with option three, . Best regards Thomas Best regards Thomas Sendt fra min Macbook Pro via Apple mail
Den 19. apr. 2026 kl. 14.50 skrev Harri Pasanen via MBraille-Test <mbraille-test@lists.mpaja.com>:
Hi,
I'm wondering what would be the best way to address this.
have a longer audio beep / effect when transferring to command mode, or different user selectable beeps. have maybe two vibrations to indicate it change the gesture for command mode, or have it configurable, similar to way undo gesture is configurable in the settings.
Any opinions?
Best regards, Harri
On Friday, April 17th, 2026 at 11:33 PM, Ioana Gandrabur via MBraille-Test <mbraille-test@lists.mpaja.com> wrote:
That is very powerful and useful. <> My only concern is when gestures get triggered by accident and one is not aware that you’re issuing a command or, as I reported in separate feedback, sometimes one ends up in command mode without sound indication by accident and it can be confusing.
Best,
Ioana
Ioana Gandrabur
Peer trainer / Paire Formatrice
Ioana.gandrabur@celalibrary.ca <mailto:Ioana.gandrabur@celalibrary.ca> 437 291-4095
www.celalibrary.ca <http://www.celalibrary.ca/> www.bibliocaeb.ca <http://www.bibliocaeb.ca/> I respectfully acknowledge that I live and work on the traditional, unceded lands of the Kanien’kehá:ka (Mohawk) Nation — a historic gathering place for many First Peoples, including the Haudenosaunee, Anishinaabeg, Huron-Wendat, and others.
Je reconnais respectueusement que je vis et travaille sur les terres traditionnelles non cédées de la nation kanien’kehá:ka (mohawk) — un lieu de rencontre historique pour de nombreux peuples autochtones, Anishinaabeg, les Hurons-Wendat et d’autres.
From: Harri Pasanen via MBraille-Test <mbraille-test@lists.mpaja.com> Sent: Friday, April 17, 2026 3:58 PM To: This list is for MBraille testers. You will get access to beta versions and latest features still in development. <mbraille-test@lists.mpaja.com> Cc: Harri Pasanen <harri@mpaja.com> Subject: [MBraille-Test] Re: 0.9.29: Notes on different areas
Hi,
It is a feature, the command mode is implicitly activated with holding dot 4 and swiping up or down to browse command history. So no need to got to command mode first.
Best regards,
Harri
On Friday, April 17th, 2026 at 10:09 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote:
Hi Harri!
Sorry if I was unclear about that part.
Is it a feature or a bug that holding down dot 4 and swiping up/down will move through the command history?
From what I read in the help the history should only work inside the command mode. If this is a feature, I really like that, and it gives MBraille a blast from the past. :)
I only thought the command history was possible to navigate through when command mode was activated first.
Best regards Thomas
Sendt fra min Macbook Pro via Apple mail
Den 17. apr. 2026 kl. 21.02 skrev Harri Pasanen via MBraille-Test <mbraille-test@lists.mpaja.com>:
Hi Thomas,
I'm going through your feedback below. The following I did not quite grasp:
Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor.
What do you mean? Any text in the editor should be passed to the command as usual.
Best regards,
Harri
On Wednesday, April 15th, 2026 at 11:16 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote:
Hi Harri!
Here are a few notes/observations I have collected since 0.9.28 and 0.9.29. Hope some of this is useful. Textbuffer
When text buffer is activated for the first time: Focus is not moved to the text field, but stays on the unlabeled button which closes the text buffer I have to swipe to the text field to make sure focus is in the right place. This is especially important for Braille display users since they aren't sure that the cursor is vissible on the screen, so they have to make a few gestures/keypresses to be able to entering Braille into the field and follow their typing.
goto command can not find apps on device. I have an app on my device named: Smartthings from Samsung. If I type: goto smartthings followed by a newline, MBraille returns app not found. Why can't MBraille find the app, if it doesn't look in a premade list of apps? This is true for both braille editor and external keyboard mode.
Text buffer: Audio ducking is not suspended
As noticed in another thread about audio ducking I found a workaround for this behaviour. This is however not working when using external keyboard mode.
Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor.
Request: Can apps like Todoist be supported in a future version? Todoist should have a good acccessibility rank both on iOS and Android. I use Todoist for almost anything, I have started to make notes for MBraille observations as of lately. I have ben in contact with their support, and they are really interested in accessibility, also if they by accident breaks something.
Editor: Promp for saving if a file is open This was drawn to my attention, when I looked for adding aliases to alias.mb I opened the alias.mb via the open command. I entered a few lines, and wanted to close the file. MBraille closed the file and my edits were lost. I wonder if a check can be made, so MBraille will Promt: Save changes to "filename"? Yes, no?
Future feature request: Command to switch between keyboard modes This might almost never be used, but I would really like for a setting that allows me to switch between braille input on screen and external keyboard mode. Muy first thought was trying to make MBraille smart enough, so it would switch mode if it detected input from an external device, but I think that is almost impossible to program.
Text buffer: The label/help text for the edit field is repeated when reading the text. It would be fine, if the text for the edit field itself was: Type text here.
Notes on generated help file:
There are a few places where formatting is escaped. For example under the paragraph: Multiple lines in aliases There is a list, but the blank line before the 1. is missing (I guess), and therefor the list is treated as regular text.
Hope some of this is useful.
Best regards Thomas
Sendt fra min Macbook Pro via Apple mail
_______________________________________________ MBraille-Test mailing list -- mbraille-test@lists.mpaja.com To unsubscribe send an email to mbraille-test-leave@lists.mpaja.com
Privacy Disclaimer - Français à suivre This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary, and confidential. If you are not the intended recipient, you are notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately. ----------------------------------------------------------------------------------- Déclaration de confidentialité Le présent courrier électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. Si ce message vous a été transmis par erreur, veuillez en informer l'expéditeur et le supprimer immédiatement.
_______________________________________________ MBraille-Test mailing list -- mbraille-test@lists.mpaja.com To unsubscribe send an email to mbraille-test-leave@lists.mpaja.com
Hi, Instead of changing the behaviour now, I'll introduce another set command to try. set hold [hold-duration-in-ms] For example set hold 500 would require half a second hold before it is recognized as hold. Currently the hard-coded default is 300 ms. I suspect that you can improve the behavior for you by slightly increasing the required hold threshold. This will be in the next version. Best regards, Harri On Tuesday, April 21st, 2026 at 9:11 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote:
Hi Harri!
I have thought about the situation, and I think I have an idea of what is going on. The issue is that when I type quickly, I accidentally activate Dot 4, which triggers the Command History mode. I then continue typing, unaware that MBraille has switched to Command Mode.
Therefore, I believe it would be a good idea to rethink this feature. I suggest that Command History mode remains in MBraille, but that Command Mode must be activated *before* Dot 4 and a swipe up or down allows the user to cycle through the history items.
The same thing happens with Dot 1 when I type fast; I frequently receive notifications stating that no further spell suggestions are available.
I hope this is somewhat useful.
Best regards, Thomas
Sendt fra min iPhone via BrailleSense U2/MBraille
Den 19. apr. 2026 kl. 20.08 skrev Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com>:
Hi Harri!
I have only seen this issue due to dot 4 being hold down triggered by lag/swipe sensitivity. The three finger swipe up have never ben an issue for me.
I would go with option three, .
Best regards Thomas Best regards Thomas
Sendt fra min Macbook Pro via Apple mail
Den 19. apr. 2026 kl. 14.50 skrev Harri Pasanen via MBraille-Test <mbraille-test@lists.mpaja.com>:
Hi,
I'm wondering what would be the best way to address this.
- have a longer audio beep / effect when transferring to command mode, or different user selectable beeps. - have maybe two vibrations to indicate it - change the gesture for command mode, or have it configurable, similar to way undo gesture is configurable in the settings.
Any opinions?
Best regards, Harri
On Friday, April 17th, 2026 at 11:33 PM, Ioana Gandrabur via MBraille-Test <mbraille-test@lists.mpaja.com> wrote:
[That is very powerful and useful.]
My only concern is when gestures get triggered by accident and one is not aware that you’re issuing a command or, as I reported in separate feedback, sometimes one ends up in command mode without sound indication by accident and it can be confusing.
Best,
Ioana
Ioana Gandrabur
Peer trainer / Paire Formatrice
Ioana.gandrabur@celalibrary.ca
437 291-4095
[www.celalibrary.ca](http://www.celalibrary.ca/)
[www.bibliocaeb.ca](http://www.bibliocaeb.ca/)
I respectfully acknowledge that I live and work on the traditional, unceded lands of the Kanien’kehá:ka (Mohawk) Nation — a historic gathering place for many First Peoples, including the Haudenosaunee, Anishinaabeg, Huron-Wendat, and others.
Je reconnais respectueusement que je vis et travaille sur les terres traditionnelles non cédées de la nation kanien’kehá:ka (mohawk) — un lieu de rencontre historique pour de nombreux peuples autochtones, Anishinaabeg, les Hurons-Wendat et d’autres.
From: Harri Pasanen via MBraille-Test <mbraille-test@lists.mpaja.com> Sent: Friday, April 17, 2026 3:58 PM To: This list is for MBraille testers. You will get access to beta versions and latest features still in development. <mbraille-test@lists.mpaja.com> Cc: Harri Pasanen <harri@mpaja.com> Subject: [MBraille-Test] Re: 0.9.29: Notes on different areas
Hi,
It is a feature, the command mode is implicitly activated with holding dot 4 and swiping up or down to browse command history. So no need to got to command mode first.
Best regards,
Harri
On Friday, April 17th, 2026 at 10:09 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote:
Hi Harri!
Sorry if I was unclear about that part.
Is it a feature or a bug that holding down dot 4 and swiping up/down will move through the command history?
From what I read in the help the history should only work inside the command mode. If this is a feature, I really like that, and it gives MBraille a blast from the past. :)
I only thought the command history was possible to navigate through when command mode was activated first.
Best regards Thomas
Sendt fra min Macbook Pro via Apple mail
> Den 17. apr. 2026 kl. 21.02 skrev Harri Pasanen via MBraille-Test <mbraille-test@lists.mpaja.com>: > > Hi Thomas, > > I'm going through your feedback below. The following I did not quite grasp: > > Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john > in an empty buffer will allow an empty message to be created. > This is not true, if there is any text in the editor. > > What do you mean? Any text in the editor should be passed to the command as usual. > > Best regards, > > Harri > > On Wednesday, April 15th, 2026 at 11:16 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote: > >> Hi Harri! >> >> Here are a few notes/observations I have collected since 0.9.28 and 0.9.29. Hope some of this is useful. >> Textbuffer >> >> When text buffer is activated for the first time: >> Focus is not moved to the text field, but stays on the unlabeled button which closes the text buffer >> I have to swipe to the text field to make sure focus is in the right place. This is especially important for Braille display users since they aren't sure that the cursor is vissible on the screen, so they have to make a few gestures/keypresses to be able to entering Braille into the field and follow their typing. >> >> goto command can not find apps on device. >> I have an app on my device named: Smartthings from Samsung. >> If I type: >> goto smartthings >> followed by a newline, MBraille returns app not found. Why can't MBraille find the app, if it doesn't look in a premade list of apps? >> This is true for both braille editor and external keyboard mode. >> >> Text buffer: Audio ducking is not suspended >> >> As noticed in another thread about audio ducking I found a workaround for this behaviour. This is however not working when using external keyboard mode. >> >> Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john >> in an empty buffer will allow an empty message to be created. >> This is not true, if there is any text in the editor. >> >> Request: Can apps like Todoist be supported in a future version? >> Todoist should have a good acccessibility rank both on iOS and Android. I use Todoist for almost anything, I have started to make notes for MBraille observations as of lately. I have ben in contact with their support, and they are really interested in accessibility, also if they by accident breaks something. >> >> Editor: Promp for saving if a file is open >> This was drawn to my attention, when I looked for adding aliases to alias.mb >> I opened the alias.mb via the open command. >> I entered a few lines, and wanted to close the file. >> MBraille closed the file and my edits were lost. >> I wonder if a check can be made, so MBraille will Promt: Save changes to "filename"? Yes, no? >> >> Future feature request: Command to switch between keyboard modes >> This might almost never be used, but I would really like for a setting that allows me to switch between braille input on screen and external keyboard mode. Muy first thought was trying to make MBraille smart enough, so it would switch mode if it detected input from an external device, but I think that is almost impossible to program. >> >> Text buffer: >> The label/help text for the edit field is repeated when reading the text. >> It would be fine, if the text for the edit field itself was: >> Type text here. >> >> Notes on generated help file: >> >> There are a few places where formatting is escaped. For example under the paragraph: >> Multiple lines in aliases >> There is a list, but the blank line before the 1. is missing (I guess), and therefor the list is treated as regular text. >> >> Hope some of this is useful. >> >> Best regards Thomas >> >> Sendt fra min Macbook Pro via Apple mail > > _______________________________________________ > MBraille-Test mailing list -- mbraille-test@lists.mpaja.com > To unsubscribe send an email to mbraille-test-leave@lists.mpaja.com
Privacy Disclaimer - Français à suivre This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary, and confidential. If you are not the intended recipient, you are notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately. ----------------------------------------------------------------------------------- Déclaration de confidentialité Le présent courrier électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. Si ce message vous a été transmis par erreur, veuillez en informer l'expéditeur et le supprimer immédiatement.
_______________________________________________ MBraille-Test mailing list -- mbraille-test@lists.mpaja.com To unsubscribe send an email to mbraille-test-leave@lists.mpaja.com
_______________________________________________ MBraille-Test mailing list -- mbraille-test@lists.mpaja.com To unsubscribe send an email to mbraille-test-leave@lists.mpaja.com
Hi again, Regarding goto command app targets: On iOS I have to explicitly add all apps that can be launched. If I recall there is a limit of maximum 60 app targets. I just added todoist and smartthings from Samsung, On Android, MBraille can discover all applications installed on the device, so everything should work. Btw. Android audio should have gotten a fair bit more fluid over the past few releases. Best regards, Harri On Friday, April 17th, 2026 at 10:09 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote:
Hi Harri!
Sorry if I was unclear about that part. Is it a feature or a bug that holding down dot 4 and swiping up/down will move through the command history? From what I read in the help the history should only work inside the command mode. If this is a feature, I really like that, and it gives MBraille a blast from the past. :) I only thought the command history was possible to navigate through when command mode was activated first.
Best regards Thomas
Sendt fra min Macbook Pro via Apple mail
Den 17. apr. 2026 kl. 21.02 skrev Harri Pasanen via MBraille-Test <mbraille-test@lists.mpaja.com>:
Hi Thomas,
I'm going through your feedback below. The following I did not quite grasp:
Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor.
What do you mean? Any text in the editor should be passed to the command as usual.
Best regards, Harri
On Wednesday, April 15th, 2026 at 11:16 PM, Thomas Byskov Dalgaard via MBraille-Test <mbraille-test@lists.mpaja.com> wrote:
Hi Harri!
Here are a few notes/observations I have collected since 0.9.28 and 0.9.29. Hope some of this is useful. Textbuffer
When text buffer is activated for the first time: Focus is not moved to the text field, but stays on the unlabeled button which closes the text buffer I have to swipe to the text field to make sure focus is in the right place. This is especially important for Braille display users since they aren't sure that the cursor is vissible on the screen, so they have to make a few gestures/keypresses to be able to entering Braille into the field and follow their typing.
goto command can not find apps on device. I have an app on my device named: Smartthings from Samsung. If I type: goto smartthings followed by a newline, MBraille returns app not found. Why can't MBraille find the app, if it doesn't look in a premade list of apps? This is true for both braille editor and external keyboard mode.
Text buffer: Audio ducking is not suspended
As noticed in another thread about audio ducking I found a workaround for this behaviour. This is however not working when using external keyboard mode.
Braille editor: When the editor is empty hold dot 4 and swipe up/down will return the last commands even if command mode isn't active. Commands can also be executed, like: sms john in an empty buffer will allow an empty message to be created. This is not true, if there is any text in the editor.
Request: Can apps like Todoist be supported in a future version? Todoist should have a good acccessibility rank both on iOS and Android. I use Todoist for almost anything, I have started to make notes for MBraille observations as of lately. I have ben in contact with their support, and they are really interested in accessibility, also if they by accident breaks something.
Editor: Promp for saving if a file is open This was drawn to my attention, when I looked for adding aliases to alias.mb I opened the alias.mb via the open command. I entered a few lines, and wanted to close the file. MBraille closed the file and my edits were lost. I wonder if a check can be made, so MBraille will Promt: Save changes to "filename"? Yes, no?
Future feature request: Command to switch between keyboard modes This might almost never be used, but I would really like for a setting that allows me to switch between braille input on screen and external keyboard mode. Muy first thought was trying to make MBraille smart enough, so it would switch mode if it detected input from an external device, but I think that is almost impossible to program.
Text buffer: The label/help text for the edit field is repeated when reading the text. It would be fine, if the text for the edit field itself was: Type text here.
Notes on generated help file:
There are a few places where formatting is escaped. For example under the paragraph: Multiple lines in aliases There is a list, but the blank line before the 1. is missing (I guess), and therefor the list is treated as regular text.
Hope some of this is useful.
Best regards Thomas
Sendt fra min Macbook Pro via Apple mail
_______________________________________________ MBraille-Test mailing list -- mbraille-test@lists.mpaja.com To unsubscribe send an email to mbraille-test-leave@lists.mpaja.com
participants (3)
-
Harri Pasanen -
Ioana Gandrabur -
Thomas Byskov Dalgaard