summaryrefslogtreecommitdiffstats
path: root/ChangeLog
diff options
context:
space:
mode:
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog6
1 files changed, 6 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index 91457fa..a074956 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2004-11-11 Reinhard Max <max@suse.de>
+
+ * generic/tkEvent.c (InvokeInputMethods): Call XSetICFocus
+ whenever the window receives focus. This fixes bug #905830 but
+ avoids #1000051.
+
2004-11-11 Daniel Steffen <das@users.sourceforge.net>
* generic/tkMain.c:
E, the parameter type changes to wchar_t *. .AP Tcl_AppInitProc *appInitProc in Address of an application-specific initialization procedure. The value for this argument is usually \fBTcl_AppInit\fR. .BE .SH DESCRIPTION .PP \fBTk_Main\fR acts as the main program for most Tk-based applications. Starting with Tk 4.0 it is not called \fBmain\fR anymore because it is part of the Tk library and having a function \fBmain\fR in a library (particularly a shared library) causes problems on many systems. Having \fBmain\fR in the Tk library would also make it hard to use Tk in C++ programs, since C++ programs must have special C++ \fBmain\fR functions. .PP Normally each application contains a small \fBmain\fR function that does nothing but invoke \fBTk_Main\fR. \fBTk_Main\fR then does all the work of creating and running a \fBwish\fR-like application. .PP When it is has finished its own initialization, but before it processes commands, \fBTk_Main\fR calls the procedure given by the \fIappInitProc\fR argument. This procedure provides a .QW hook for the application to perform its own initialization, such as defining application-specific commands. The procedure must have an interface that matches the type \fBTcl_AppInitProc\fR: .CS typedef int \fBTcl_AppInitProc\fR( Tcl_Interp *\fIinterp\fR); .CE \fIAppInitProc\fR is almost always a pointer to \fBTcl_AppInit\fR; for more details on this procedure, see the documentation for \fBTcl_AppInit\fR. .PP \fBTk_Main\fR functions much the same as \fBTcl_Main\fR. In particular, \fBTk_Main\fR supports both an interactive mode and a startup script mode, with the file name and encoding of a startup script under the control of the \fBTcl_SetStartupScript\fR and \fBTcl_GetStartupScript\fR routines. However it calls \fBTk_MainLoop\fR after processing any supplied script, and in interactive uses events registered with \fBTcl_CreateFileHandler\fR to process user input. .SH "SEE ALSO" Tcl_DoOneEvent(3) .SH KEYWORDS application-specific initialization, command-line arguments, main program