Move code around

This commit is contained in:
Jean-Marc Lasgouttes 2018-05-02 12:43:10 +02:00
parent 7f035b51a0
commit 22de5c972a
2 changed files with 16 additions and 14 deletions

View File

@ -2239,6 +2239,12 @@ void Cursor::screenUpdateFlags(Update::flags f) const
}
void Cursor::noScreenUpdate() const
{
disp_.screenUpdate(Update::None);
}
void Cursor::forceBufferUpdate() const
{
disp_.forceBufferUpdate();
@ -2257,12 +2263,6 @@ bool Cursor::needBufferUpdate() const
}
void Cursor::noScreenUpdate() const
{
disp_.screenUpdate(Update::None);
}
Font Cursor::getFont() const
{
// The logic here should more or less match to the

View File

@ -394,16 +394,11 @@ public:
void undispatched() const;
/// the event was already dispatched
void dispatched() const;
/// Set which screen update should be done
/// Describe the screen update that should be done
void screenUpdateFlags(Update::flags f) const;
/// Forces an updateBuffer() call
void forceBufferUpdate() const;
/// Removes any pending updateBuffer() call
void clearBufferUpdate() const;
/// Do we need to call updateBuffer()?
bool needBufferUpdate() const;
/**
* don't call update() when done
* Reset update flags to Update::None.
*
* Should only be called by an inset's doDispatch() method. It means:
* I handled that request and I can reassure you that the screen does
@ -414,6 +409,13 @@ public:
*/
void noScreenUpdate() const;
/// Forces an updateBuffer() call
void forceBufferUpdate() const;
/// Removes any pending updateBuffer() call
void clearBufferUpdate() const;
/// Do we need to call updateBuffer()?
bool needBufferUpdate() const;
/// Repopulate the slices insets from bottom to top. Useful
/// for stable iterators or Undo data.
void sanitize();