- gtk_statusbar_pop(GTK_STATUSBAR(info_bar), file_ctx);
- if (err == 0) {
- if (!save_filtered && !save_marked) {
- /* We saved the entire capture, not just some packets from it.
- Open and read the file we saved it to.
-
- XXX - this is somewhat of a waste; we already have the
- packets, all this gets us is updated file type information
- (which we could just stuff into "cf"), and having the new
- file be the one we have opened and from which we're reading
- the data, and it means we have to spend time opening and
- reading the file, which could be a significant amount of
- time if the file is large. */
- cf->user_saved = TRUE;
-
- if ((err = open_cap_file(fname, FALSE, cf)) == 0) {
- /* XXX - report errors if this fails? */
- switch (read_cap_file(cf, &err)) {
-
- case READ_SUCCESS:
- case READ_ERROR:
- /* Just because we got an error, that doesn't mean we were unable
- to read any of the file; we handle what we could get from the
- file. */
- break;
-
- case READ_ABORTED:
- /* The user bailed out of re-reading the capture file; the
- capture file has been closed - just return (without
- changing any menu settings; "close_cap_file()" set them
- correctly for the "no capture file open" state). */
- return 0;
- }
- set_menus_for_unsaved_capture_file(FALSE);
+ statusbar_pop_file_msg();
+ if (!save_filtered && !save_marked) {
+ /* We saved the entire capture, not just some packets from it.
+ Open and read the file we saved it to.
+
+ XXX - this is somewhat of a waste; we already have the
+ packets, all this gets us is updated file type information
+ (which we could just stuff into "cf"), and having the new
+ file be the one we have opened and from which we're reading
+ the data, and it means we have to spend time opening and
+ reading the file, which could be a significant amount of
+ time if the file is large. */
+ cf->user_saved = TRUE;
+
+ if ((err = open_cap_file(fname, FALSE, cf)) == 0) {
+ /* XXX - report errors if this fails?
+ What should we return if it fails or is aborted? */
+ switch (read_cap_file(cf, &err)) {
+
+ case READ_SUCCESS:
+ case READ_ERROR:
+ /* Just because we got an error, that doesn't mean we were unable
+ to read any of the file; we handle what we could get from the
+ file. */
+ break;
+
+ case READ_ABORTED:
+ /* The user bailed out of re-reading the capture file; the
+ capture file has been closed - just return (without
+ changing any menu settings; "close_cap_file()" set them
+ correctly for the "no capture file open" state). */
+ break;