File: run_loop_testing.h

package info (click to toggle)

chromium-browser 41.0.2272.118-1

links: PTS, VCS
area: main
in suites: jessie-kfreebsd
size: 2,189,132 kB
sloc: cpp: 9,691,462; ansic: 3,341,451; python: 712,689; asm: 518,779; xml: 208,926; java: 169,820; sh: 119,353; perl: 68,907; makefile: 28,311; yacc: 13,305; objc: 11,385; tcl: 3,186; cs: 2,225; sql: 2,217; lex: 2,215; lisp: 1,349; pascal: 1,256; awk: 407; ruby: 155; sed: 53; php: 14; exp: 11

file content (29 lines) | stat: -rw-r--r-- 1,130 bytes

parent folder | download | duplicates (2)

// Copyright (c) 2011 The Chromium Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

#ifndef CHROME_BROWSER_UI_COCOA_RUN_LOOP_TESTING_H_
#define CHROME_BROWSER_UI_COCOA_RUN_LOOP_TESTING_H_

namespace chrome {
namespace testing {

// A common pattern in Chromium is to get a selector to execute on the next
// iteration of the outermost run loop, done like so:
//
//    [someObj performSelector:@selector(someSel:) withObject:nil afterDelay:0];
//
// This is used when performing the work will negatively affect something
// currently on the stack. Unfortunately this also affects the testability of
// objects that do this. A call to this function will pump work like this from
// the event queue and run it until all such work, as of the time of calling
// this, has been processed.
//
// Note that this is not a NSApplication-based loop, and so things like NSEvents
// are *not* pumped from the event queue.
void NSRunLoopRunAllPending();

}  // namespace testing
}  // namespace chrome

#endif  // CHROME_BROWSER_UI_COCOA_RUN_LOOP_TESTING_H_