Skip to content
Snippets Groups Projects
Commit 3bf0ee92 authored by ram's avatar ram
Browse files

fix some problems.

parent beedd292
No related branches found
No related tags found
No related merge requests found
/* -*- Mode: C -*- */ /* -*- Mode: C -*- */
/* $Header: /Volumes/share2/src/cmucl/cvs2git/cvsroot/src/motif/server/timer-support.c,v 1.1 1994/10/27 17:44:53 ram Exp $ */ /* $Header: /Volumes/share2/src/cmucl/cvs2git/cvsroot/src/motif/server/timer-support.c,v 1.2 1994/10/29 03:00:32 ram Exp $ */
/* timer_support.c -- /* timer_support.c --
* Extension to CMUCL Motif Interface. Adding missing call for * Extension to CMUCL Motif Interface. Adding missing call for
...@@ -44,6 +44,50 @@ ...@@ -44,6 +44,50 @@
* Functions * Functions
*/ */
void
reply_with_xt_interval(message_t message, XtIntervalId timer) {
reply_with_integer(message, (unsigned long) timer);
/* Pretty redundant! */
}
void
RawTimerHandler(XtPointer lisp_timer_id, XtIntervalId* timer) {
int exit_value;
extern int end_callback_loop;
message_t reply = message_new(next_serial++);
message_add_packet(reply);
message_put_dblword(reply, TIMEOUT_REPLY); /* This is new. */
message_write_int(reply, (unsigned long) *lisp_timer_id);
message_write_int(reply, (unsgined long) *timer);
message_send(client_socket, reply);
message_free(reply);
exit_value = end_callback_loop++;
/* Code lifted from original CMU */
/* *** This version handles no events until callbacks are done
*** processing
*/
while( exit_value<end_callback_loop )
XtAppProcessEvent(app_context,XtIMAlternateInput);
/* *** Use this version to allow callbacks to occur during callback
*** processing
*** In general, this is not something the you want to do. For instance,
*** the callback_info mechanism for supporting modifications to the
*** callback structure would no longer work if callbacks could be nested.
while( exit_value<end_callback_loop ) {
XtAppNextEvent(app_context, &event);
XtDispatchEvent(&event);
}
*/
}
/* RXtAppAddTimeOut -- */ /* RXtAppAddTimeOut -- */
int int
...@@ -81,42 +125,3 @@ RXtAppAddTimeOut(message_t message) ...@@ -81,42 +125,3 @@ RXtAppAddTimeOut(message_t message)
reply_with_xt_interval(message, timer); reply_with_xt_interval(message, timer);
} }
void
reply_with_xt_interval(message_t message, XtIntervalId timer) {
reply_with_integer(message, (unsigned long) timer);
/* Pretty redundant! */
}
void
RawTimerHandler(XtPointer lisp_timer_id, XtIntervalId* timer) {
message_t replay = message_new(next_serial++);
message_add_packet(reply);
message_put_dblword(reply, TIMEOUT_REPLY); /* This is new. */
message_write_int(reply, (unsigned long) *lisp_timer_id);
message_write_int(reply, (unsigned long) *timer);
message_send(client_socket, reply);
message_free(reply);
exit_value = end_callback_loop++;
/* Code lifted from original CMU */
/* *** This version handles no events until callbacks are done
*** processing
*/
while( exit_value<end_callback_loop )
XtAppProcessEvent(app_context,XtIMAlternateInput);
/* *** Use this version to allow callbacks to occur during callback
*** processing
*** In general, this is not something the you want to do. For instance,
*** the callback_info mechanism for supporting modifications to the
*** callback structure would no longer work if callbacks could be nested.
while( exit_value<end_callback_loop ) {
XtAppNextEvent(app_context, &event);
XtDispatchEvent(&event);
}
*/
}
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment