You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by mdcurran on 2014-01-17 06:15
If moving the caret around a document in Microsoft Word with report spelling errors turned on (default), there is a noticable lag before the braille display is updated. Turning off reporting of spelling errors definitely reduces the lag.
When collecting text from MS Word, we currently check for a spelling error on every word, which would mean a great deal of calls.
Perhaps we should collect all spelling error offsets at the start and match them as we move through the text by word.
The text was updated successfully, but these errors were encountered:
Comment 4 by Michael Curran <mick@... on 2014-02-02 10:56
In [7ac923a]:
Fix a possible buffer overrun which may have caused a crash in MS Word (picked up by MSVC RTC). Re #3785
VT_BOOL uses 16 bit values, so either VARIANT_BOOL or BOOL should be used. bool (c++) is only 8 bit which is not enough. The rest of calls with VT_BOOL were using BOOL 32 bit.
Reported by mdcurran on 2014-01-17 06:15
If moving the caret around a document in Microsoft Word with report spelling errors turned on (default), there is a noticable lag before the braille display is updated. Turning off reporting of spelling errors definitely reduces the lag.
When collecting text from MS Word, we currently check for a spelling error on every word, which would mean a great deal of calls.
Perhaps we should collect all spelling error offsets at the start and match them as we move through the text by word.
The text was updated successfully, but these errors were encountered: