path: root/capture.c
diff options
authorUlf Lamping <ulf.lamping@web.de>2005-09-20 08:42:35 +0000
committerUlf Lamping <ulf.lamping@web.de>2005-09-20 08:42:35 +0000
commit831c54c4f5b15e8d8fce18bd6f6d08974d689d56 (patch)
tree0537131334ea0bf565922349bf410e468fc3ad21 /capture.c
parent776776960def92068adf7ada8e341aa01f6284c3 (diff)
add two new callbacks:
cf_cb_file_closing (called before closing a capture file) cf_cb_file_closed will be called afterwards, but both only if a file is really closed as cf_close is called more often ... If we are closing large capture files (~20MB), the screen looks ugly while the file is closed. Change this so the screen will immediately go back to initial state and a dialog (without buttons) is shown that the file is currently closed. As the operation which takes most of the time to close the file is a single eth_clist_clear call, we can't use a progress bar here. cf_cb_live_capture_stopping: called when the user wants to stop the capture (toolbar or menu clicked). At least on Win32, the time between this and the actual stop completed can be noticeable (1-2 seconds), so the user doesn't know if the button press did anything at all. Do something similar as above, show a dialog box without buttons to inform that the close is in progress. svn path=/trunk/; revision=15891
Diffstat (limited to 'capture.c')
1 files changed, 3 insertions, 0 deletions
diff --git a/capture.c b/capture.c
index 12f9cbe3f3..c89feea5f9 100644
--- a/capture.c
+++ b/capture.c
@@ -119,6 +119,8 @@ capture_stop(capture_options *capture_opts)
+ cf_callback_invoke(cf_cb_live_capture_stopping, capture_opts);
/* stop the capture child gracefully */
@@ -310,6 +312,7 @@ capture_input_new_packets(capture_options *capture_opts, int to_read)
XXX - abort on a read error? */
cf_callback_invoke(cf_cb_live_capture_update_continue, capture_opts->cf);
+ /* update the main window, so we get events (e.g. from the stop toolbar button) */