HomeSort by relevance Sort by last modified time
    Searched defs:didUpdateBackingStoreState (Results 1 - 2 of 2) sorted by null

  /external/webkit/Source/WebKit2/UIProcess/
DrawingAreaProxy.h 108 virtual void didUpdateBackingStoreState(uint64_t backingStoreStateID, const UpdateInfo&, const LayerTreeContext&) { }
DrawingAreaProxyImpl.cpp 83 // Wait for a DidUpdateBackingStoreState message that contains the new bits before we paint
88 // Dispatching DidUpdateBackingStoreState (either beneath sendUpdateBackingStoreState or
176 void DrawingAreaProxyImpl::didUpdateBackingStoreState(uint64_t backingStoreStateID, const UpdateInfo& updateInfo, const LayerTreeContext& layerTreeContext)
285 // Wait for the DidUpdateBackingStoreState message. Normally we don this in DrawingAreaProxyImpl::paint, but that
302 // FIXME: waitForAndDispatchImmediately will always return the oldest DidUpdateBackingStoreState message that
303 // hasn't yet been processed. But it might be better to skip ahead to some other DidUpdateBackingStoreState
304 // message, if multiple DidUpdateBackingStoreState messages are waiting to be processed. For instance, we could
307 // The timeout, in seconds, we use when waiting for a DidUpdateBackingStoreState message when we're asked to paint.
309 m_webPageProxy->process()->connection()->waitForAndDispatchImmediately<Messages::DrawingAreaProxy::DidUpdateBackingStoreState>(m_webPageProxy->pageID(), didUpdateBackingStoreStateTimeout);

Completed in 201 milliseconds