Use custom column check function for custom columns to make sure the dfilter
is always primed when needed. This ensures more than just the first row has a custom column's information in it. svn path=/trunk/; revision=24413
This commit is contained in:
parent
1c5dddbd68
commit
c7d656555a
|
@ -276,7 +276,7 @@ col_custom_set_fstr(const gchar *field_name, const gchar *format, ...)
|
|||
va_list ap;
|
||||
int i;
|
||||
|
||||
if (!check_col(ci, COL_CUSTOM))
|
||||
if (!have_custom_cols(ci))
|
||||
return;
|
||||
|
||||
va_start(ap, format);
|
||||
|
@ -302,7 +302,7 @@ col_custom_prime_edt(epan_dissect_t *edt, column_info *cinfo)
|
|||
ci = cinfo; /* Save this into the static variable ci for use by
|
||||
* col_custom_set_fstr() later. */
|
||||
|
||||
if(!check_col(cinfo, COL_CUSTOM))
|
||||
if(!have_custom_cols(cinfo))
|
||||
return;
|
||||
|
||||
for (i = cinfo->col_first[COL_CUSTOM];
|
||||
|
|
Loading…
Reference in New Issue