diff options
| author | Miklos Vajna <vmiklos@collabora.co.uk> | 2016-09-29 12:49:23 +0200 |
|---|---|---|
| committer | Miklos Vajna <vmiklos@collabora.co.uk> | 2016-09-29 12:53:02 +0200 |
| commit | d5263c2c564c88e3dafe4c1ab8d3d9c1c48ede73 (patch) | |
| tree | 191b3c39c3c78b3766a7d6c5ebf6b1d1dda5d3c3 /include/comphelper/lok.hxx | |
| parent | 785eb0ed14cde731c2795f68f004f0b811cfe387 (diff) | |
LOK: conditionally include part number in invalidation payload
Since desktop/ code queues, compresses and only emits callbacks on idle,
it's possible that two invalidations are in the queue, and there was a
setPart() call between them. In this case it's impossible to tell what
part the invalidation was sent for.
Fix this by conditionally including the part number in the invalidation
payload. It's off by default, a new feature flag is added to request
this behavior.
gtktiledviewer enables this feature flag by default, though just to show
the part number in the debug output. Android doesn't enable it.
Change-Id: I73e6def848c0eb61d64e71026002c7a0e750aab4
Diffstat (limited to 'include/comphelper/lok.hxx')
| -rw-r--r-- | include/comphelper/lok.hxx | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/include/comphelper/lok.hxx b/include/comphelper/lok.hxx index 8afd3d82a77d..529694ce0acc 100644 --- a/include/comphelper/lok.hxx +++ b/include/comphelper/lok.hxx @@ -43,10 +43,10 @@ COMPHELPER_DLLPUBLIC bool isActive(); COMPHELPER_DLLPUBLIC void setLocalRendering(bool bLocalRendering = true); COMPHELPER_DLLPUBLIC bool isLocalRendering(); -/// Check whether clients register a callback for each view. -COMPHELPER_DLLPUBLIC bool isViewCallback(); -/// Set whether clients register a callback for each view. -COMPHELPER_DLLPUBLIC void setViewCallback(bool bViewCallback); +/// Check whether clients want a part number in an invalidation payload. +COMPHELPER_DLLPUBLIC bool isPartInInvalidation(); +/// Set whether clients want a part number in an invalidation payload. +COMPHELPER_DLLPUBLIC void setPartInInvalidation(bool bPartInInvalidation); // Status indicator handling. Even if in theory there could be several status indicators active at // the same time, in practice there is only one at a time, so we don't handle any identification of |