Make the "Export Selected Packets As..." code path more like the "Save

As..." code path.

Extract the code for the "do you want to overwrite this file" and "OK,
you do - are you aware it's {user-immutable, read-only}?" code paths
into a common routine for use by both of those and, potentially, other
save/export/etc. code paths in the future.

For "Save As", allow us to save atop the current capture file, as that's
just what "Save" does if there are unsaved changes, and "safe save"
makes that work.  *Don't* allow that for "Export Selected Packets
As...", however.

The file chooser is run as a modal dialog, so we don't need to worry
about creating more than one of them or about the number of marked
packets etc. being changed out from under us.  Get rid of a bunch of
static variables.

svn path=/trunk/; revision=43060

1 files changed, 9 insertions, 0 deletions

diff --git a/ui/gtk/range_utils.h b/ui/gtk/range_utils.h
index 5c14488cf3..1c63632621 100644
--- a/ui/gtk/range_utils.h
+++ b/ui/gtk/range_utils.h
@@ -39,6 +39,15 @@
  */
 extern gboolean range_check_validity(packet_range_t *range);
 
+/** Check the validity of a packet_range_t, and put up a modal alert box if
+ ** it's not valid.
+ *
+ * @param parent the widget for the window that contained the range specification
+ * @param range the range to check
+ * @return a Boolean that's TRUE if it's valid and FALSE if it isn't
+ */
+extern gboolean range_check_validity_modal(GtkWidget *parent, packet_range_t *range);
+
 /** Create a new range widget.
  *
  * @param range the range to set