/usr/lib/ocaml/lablgtk2/gtkThread.mli is in liblablgtk2-ocaml-dev 2.14.2+dfsg-2build1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 | (**************************************************************************)
(* Lablgtk *)
(* *)
(* This program is free software; you can redistribute it *)
(* and/or modify it under the terms of the GNU Library General *)
(* Public License as published by the Free Software Foundation *)
(* version 2, with the exception described in file COPYING which *)
(* comes with the library. *)
(* *)
(* This program is distributed in the hope that it will be useful, *)
(* but WITHOUT ANY WARRANTY; without even the implied warranty of *)
(* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the *)
(* GNU Library General Public License for more details. *)
(* *)
(* You should have received a copy of the GNU Library General *)
(* Public License along with this program; if not, write to the *)
(* Free Software Foundation, Inc., 59 Temple Place, Suite 330, *)
(* Boston, MA 02111-1307 USA *)
(* *)
(* *)
(**************************************************************************)
(* $Id: gtkThread.mli 1518 2010-06-25 09:23:44Z garrigue $ *)
(* Basic functions *)
(** The main loop to use with threads. [GMain.main] does not work!
This changes [GMain.main] to call [threaded_main] rather than
[GtkMain.Main.default_main], so subsequent calls will work.
The first call sets the GUI thread, and subsequent calls
to [main] will be automatically routed through [sync] *)
val main : unit -> unit
(** Start the main loop in a new GUI thread. Do not use recursively. *)
val start : unit -> Thread.t
(** The real main function *)
val thread_main : unit -> unit
(** Forget the current GUI thread. The next call to [main]
will register its caller as GUI thread. *)
val reset : unit -> unit
(* Jobs are needed for windows, as you cannot do GTK work from
another thread.
Even under Unix some calls need to come from the main thread.
The basic idea is to either use async (if you don't need a result)
or sync whenever you call a GTK related function from another thread
(for instance with the threaded toplevel).
With sync, beware of deadlocks!
*)
(** Add an asynchronous job (to do in the main thread) *)
val async : ('a -> unit) -> 'a -> unit
(** Add a synchronous job (to do in the main thread) *)
val sync : ('a -> 'b) -> 'a -> 'b
(** Whether it is safe to call most GTK functions directly from
the current thread *)
val gui_safe : unit -> bool
(** Allow other threads to run, and process the message queue.
The following ensures that messages will be processed even
if another main loop is running:
[Glib.Timeout.add ~ms:100 ~callback:GtkThread.do_jobs] *)
val do_jobs : unit -> bool
|