HomeSort by relevance Sort by last modified time
    Searched full:kapplication (Results 1 - 4 of 4) sorted by null

  /external/libbrillo/brillo/
mime_utils_unittest.cc 16 mime::Combine(mime::types::kApplication, "json", {{"charset", "utf-8"}}));
28 EXPECT_EQ(mime::types::kApplication, s1);
mime_utils.h 21 BRILLO_EXPORT extern const char kApplication[]; // application
mime_utils.cc 16 const char mime::types::kApplication[] = "application";
  /external/dbus/doc/
dcop-howto.txt 77 KApplication has gained a method called "KApplication::dcopClient()"
81 KApplication::name() returns. In fact, if there is only a single
83 KApplication::name().
88 will return false. KApplication will catch a dcop signal and display an
103 If you never retrieve the DCOPClient pointer from KApplication, the
501 #include <kapplication.h>
505 KApplication *app;
507 app = new KApplication(argc, argv, "testit");
525 If I create the KApplication's DCOPClient, and call attach() an
    [all...]

Completed in 67 milliseconds