Luis's description is what I was thinking of when I made a suggestion a long time ago.
I frequently switch between protocol settings, for example: ANSI MAP ANSI TCAP ANSI SCCP ANSI MTP3 versus ANSI MAP ANSI TCAP ITU SCCP ITU MTP3 versus GSM MAP GSM TCAP ITU SCCP ITU MTP3 versus GSM MAP GSM TCAP ANSI SCCP ANSI MTP3 along with variations of BSSAP/BSAP and ISUP. It would be nice to use a pulldown of saved settings. It would also be nice to have filters associated to the saved settings. 90% of the time I use this filter: "BASIC" (mgcp or megaco or isup or sccplite or sccp or sip or alcap or ansi_abis or a11 or tccs or snmp) I believe the capture file is loaded a second time after the filter is applied? Thanks. -- Michael Lum Principal Software Engineer 4600 Jacombs Road +1.604.276.0055 Richmond, B.C. Canada V6V 3B1 UTStarcom Canada, Inc. CDMA Division -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Luis Ontanon Sent: February 15, 2007 2:24 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Saving settings as "Profiles" On 2/15/07, Ulf Lamping <[EMAIL PROTECTED]> wrote: > Luis Ontanon wrote: > > Overall it looks like a feasable project not something *very* > > complex to implement. > > > You might miss the most work intensive point here: how to compare / > merge two different sets in a GUI way? I do not see why there's a need to compare/merge them... I'm thinking in something like HP's high-end printers print format dialogs, there you can save a certain group of settings, and if you modify some settings you might want to save the settings (all of them) with another name. So, for example, I have a "2x2" saved setting that prints two pages per side on both sides, I might want to modify that to zoom by 110% and save it again as "2x2-110". There there's no need whatsoever to compare two sets of settings. > > Luis > > > > PS. Don't count on me for implementing it I'm already over-threaded > > as it is right now. > > > Yes, you might finish some projects (including documentation) still > being marked experimental before starting new topics ;-) Ack, I being writing too much C and too little english (and Lua). BTW, you are aware just of what's already checked in... I got plenty of unfinished projects I've never checked in (abnf2eth, diameter dictionary parser with filterable fields, Lua's "Cursor" parser-generator (based on tvbparse), and other "semi-useless" experiments that probably will never see the light). Plus the one I'm on as for now that I *have* to fiinish (because I need them for work)... Luis -- This information is top security. When you have read it, destroy yourself. -- Marshall McLuhan _______________________________________________ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev _______________________________________________ Wireshark-dev mailing list Wireshark-dev@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-dev
