Richard Heck 5577e877bb Try to move all updateBuffer() calls to a central location. We now use ... DispatchResult to store a flag that tells us whether we need a buffer update or not. So: If you find a missing one, go to an appropriate place in the dispatch and call cur.forceBufferUpdate() or, if you don't have a cursor but do have a DispatchResult, call dr.forceBufferUpdate(). There is one remaining call I could not move, in TextMetrics::redoParagraph. But this looks like an emergency call when the macro context has not been set. There are also a couple calls that are connected with buffer creation that I commented out, since the same call is done again almost immediately. But I'm not positive about those. Now the nice thing would be to do the same for updateMacros(). git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@34826 a592a061-630c-0410-9148-cb99ea01b6c8		2010-07-09 14:37:00 +00:00
..
qt4	Try to move all updateBuffer() calls to a central location. We now use	2010-07-09 14:37:00 +00:00
tests
alert.h	Extend Alert::prompt such that 4 buttons are possible. Thus, when	2010-04-19 20:44:57 +00:00
Application.h	Application: get rid of 2 virtual interface.	2010-02-09 17:25:44 +00:00
Clipboard.h
Delegates.h
FontLoader.h
FontMetrics.h
KeyModifier.h
KeySymbol.h
Makefile.am	Today is a sad day, LyXView has passed over... long live GuiView!	2010-02-09 17:06:40 +00:00
mouse_state.h
Painter.h
Selection.h
WorkArea.h	Today is a sad day, LyXView has passed over... long live GuiView!	2010-02-09 17:06:40 +00:00
WorkAreaManager.cpp	Get rid of Buffer::setReadOnly() pseudo signal.	2010-01-25 13:31:07 +00:00
WorkAreaManager.h	Get rid of Buffer::setReadOnly() pseudo signal.	2010-01-25 13:31:07 +00:00