Reported by mdcurran on 2007-11-21 03:08
When reviewing text in the current navigator object, when the object is a generic NVDA object or dos console window object, the text stays the same as it was when the object was first created. I.e. reviewing a list item in Windows task manager, as the memory or cpu usage changes, the reviewable text does not reflect this change. The reason for this is because the generic offset TextInfo class caches text to speed up navigation. What should happen is that the NVDA object itself should cache a text representation of the name/value/description text, and update it when it receives a name/value/description change event. Then the TextInfo object should always use the NVDA object's text representation cache, not its own.
Reported by mdcurran on 2007-11-21 03:08
When reviewing text in the current navigator object, when the object is a generic NVDA object or dos console window object, the text stays the same as it was when the object was first created. I.e. reviewing a list item in Windows task manager, as the memory or cpu usage changes, the reviewable text does not reflect this change. The reason for this is because the generic offset TextInfo class caches text to speed up navigation. What should happen is that the NVDA object itself should cache a text representation of the name/value/description text, and update it when it receives a name/value/description change event. Then the TextInfo object should always use the NVDA object's text representation cache, not its own.