It's OK for me on Windoze.
Are you loading Wireshark over a remote connection (X, maybe via 'ssh')
where the (couple thousand?) screen updates in a couple of seconds
might, well, take a while?
Stephen Fisher wrote:
Is it just me or does this change slow down the launching of Wireshark
noticably?
On Mon, May 07, 2007 at 05:55:47PM +0000, gal@xxxxxxxxxxxxx wrote:
http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=21716
User: gal
Date: 2007/05/07 05:55 PM
Log:
Updated splash screen for Wireshark that shows the initialisation progress.
The splash screen shows a progress bar and a percentage complete - like the progress dialog.
As dissectors are initialised and handed off the name is shown. However, the names of plugin dissectors are not shown.
The update to the make-dissector-reg shell script has been tested, though I think generally the python version is used.
Directory: /trunk/epan/
Changes Path Action
+5 -3 epan.c Modified
+5 -2 epan.h Modified
+1 -0 libwireshark.def Modified
+10 -4 proto.c Modified
+5 -2 proto.h Modified
Directory: /trunk/gtk/
Changes Path Action
+123 -4 about_dlg.c Modified
+5 -4 about_dlg.h Modified
+7 -6 main.c Modified
Directory: /trunk/tools/
Changes Path Action
+62 -9 make-dissector-reg Modified
+23 -4 make-dissector-reg.py Modified
(3 files not shown)
_______________________________________________
Wireshark-commits mailing list
Wireshark-commits@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-commits
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev