UpdateAllViews called when deleting characters

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

I have an application with multiple views where one is a CXTPSyntaxEditView.  When testing v15.1.3 I noticed (for me) an unwanted behaviour: 

If you press backspace to delete a character ALL my views are being updated - for every character you delete. 

This is because when you delete a character range CXTPSyntaxEditCtrl::InvalidateAll() will be called. This function in turn calls

pParentWnd->GetDocument()->UpdateAllViews(NULL, xtpEditHintInvalidate);

which causes all my views to update. 

Of course I could check if lHint == xtpEditHintInvalidate, however this value is 10 which happens to be a value that I also use. 

Version 15.0.2 did not have this behaviour. 

Is this 'as designed' and will not change in future implementation or will there be another fix for it? 

Thanks, 
Fredrik

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Fredrik Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 22 June 2005 Status: Offline Points: 235	Post Options Post Reply Quote Fredrik Report Post Thanks(0) Quote Reply Topic: UpdateAllViews called when deleting characters Posted: 04 October 2011 at 5:55am
	I have an application with multiple views where one is a CXTPSyntaxEditView. When testing v15.1.3 I noticed (for me) an unwanted behaviour: If you press backspace to delete a character ALL my views are being updated - for every character you delete. This is because when you delete a character range CXTPSyntaxEditCtrl::InvalidateAll() will be called. This function in turn calls pParentWnd->GetDocument()->UpdateAllViews(NULL, xtpEditHintInvalidate); which causes all my views to update. Of course I could check if lHint == xtpEditHintInvalidate, however this value is 10 which happens to be a value that I also use. Version 15.0.2 did not have this behaviour. Is this 'as designed' and will not change in future implementation or will there be another fix for it? Thanks, Fredrik
	Windows 10, Visual Studio 20157, Toolkit Pro 18.3.0