Steps to reproduce:

After installing recent alpha build (33644 and later), press Alt+NVDA+T to toggle braile mode between "follow cursors" and "speech output".

Actual behavior:

A zero division error is logged when braille mode is switched to "speech output".

Expected behavior:

No errors

NVDA logs, crash dumps and other attachments:

Log fragment (on alpha-33656,35e31582):
ERROR - extensionPoints.Action.notify (18:48:53.927) - MainThread (18176):
Error running handler <bound method BrailleHandler.showSpeechInBraille of <braille.BrailleHandler object at 0x06258ED0>> for <extensionPoints.Action object at 0x042FC250>
Traceback (most recent call last):
File "extensionPoints_init.pyc", line 56, in notify
File "extensionPoints\util.pyc", line 216, in callWithSupportedKwargs
File "braille.pyc", line 2471, in _showSpeechInBraille
File "braille.pyc", line 2057, in update
File "braille.pyc", line 1884, in _get_windowStartPos
File "braille.pyc", line 1874, in windowPosToBufferPos
ZeroDivisionError: integer division or modulo by zero

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

alpha-33656,35e31582

Windows version:

Windows 11 24H2 Insider dev (build 26120.1542)

Name and version of other software in use when reproducing the issue:

None

Other information about your system:

Used as a development workstation

Other questions

Does the issue still occur after restarting your computer?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

Started with alpha-33644,cee553df - no issues with 2024.3 and 2024.4 beta

If NVDA add-ons are disabled, is your problem still occurring?

Yes

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

Not applicable

CC @michaelDCurran, likely something coming from word wrap handling for multi-line displays.