How to reference field for display filters?

So I can not in any way doing what I want to do?

I have read the dissect_diameter_avp function, but I don't understand how this benefit for me. It must be said that I do not have a lot of convenience with the development of plugins for wireshark.

Well it's not easy to try to help you as you are not describing what you are trying to do in much detail... What does your file contain and what is the content of the packets sent? The actual text "field 1 = 10" or a TAG and a VALUE or a TAG LENGHT VALUE type field or does your file specify that the first xx bytes are field 1 then next YYY bytes are field 2 and so on.

What @Anders is describing is dynamically adding hf entries according to a configuration file.

I'm unsure if this is still a one-time initialization though and if Wireshark has to be restarted if the config file is changed.

@Anders

// according to the address of the packet
// the name and number fields
// that describe the package
// is searched for in an external file
ti = proto_tree_add_string_format(myProto_field_tree, hf_myProto_field_name, tvb, MYPROTO_DATA_OFFSET, length, fieldName, "%s", fieldName);
PROTO_ITEM_SET_GENERATED(ti);
myProto_singleField_tree = proto_item_add_subtree(ti, ett_myProto_singleField);
// I saved the value of each field
// in a structure "msg"
proto_tree_add_double_format(myProto_singleField_tree, hf_myProto_field_value, tvb, MYPROTO_DATA_OFFSET + offset, length, msg->field[i].value, "Field Value: %g", msg->field[i].value);
I want to get that for every "field" (hf_myProto_field_name) is associated
with a single value (hf_myProto_field_value), so as to be able to filter packets as in the previous example.
To make it even clearer ideas, if I knew the number (and possibly the name) of the fields, the problem did not arise, since I had only to declare different "values" (hf_myProto_value1, hf_myProto_value2, ...) and each of they would be paid one and only one field "field", but since this is not possible, I would still find a way to resolve the situation.
@grahamb
How do I add dynamically hf entries?

There is a "guide" that explains the process by which dynamically allocate arrays fields of hf? Unfortunately I am a beginner and it is not easy for me to understand how this is done in the dissector "packet-diameter". Thanks @grahamb and @Anders for the answers you have given me so far.

No guide I know of. I'll agree that packet-diameter is quite complex.

This question is now starting to get a little too complex for Ask Wireshark, you might be better off taking it to the dev mailing list.

Waiting for answers from the developers, I would continue to asks you. My case is much simpler than that of the "packet-diameter", because the fields "value" are all kind of FT_DOUBLE, so I think it is unnecessary to hash table; the only thing that will change will be the string used in the filter (FIELDABBREV) which should, at this point, I have a different name for each field "field". I already have my function that parses the external file by creating a structure "msg" field contains the name of the "field" and the corresponding "value". I guess at this point that the field "field" becomes superfluous, since all the information will be contained in the "value", to which I will assign FIELDABBREV as a string type:

myProto.field.nameField

At this point, the only question to me is, the array hf (build_dict.hf) is initialized in the function "real_proto_register_diameter()", but built in "dictionary_load()"? If so, how exactly? I hope to have been clear. Thank you for your kindness .

Or, perhaps, it would be enough for me just what he does in the "basic_avp_reginfo()"?

And yet, as you can apply a filter on the desired field if the FIELDABBREV initializes it to NULL?

hf_register_info hf[] = { { &(a->hf_value),
                  { NULL, NULL/FIELDABBREV/, ft, base, NULL, 0x0,
                  a->vendor->code ?
                  wmem_strdup_printf(wmem_epan_scope(), "vendor=%d code=%d", a->vendor->code, a->code)
                  : wmem_strdup_printf(wmem_epan_scope(), "code=%d", a->code),
                  HFILL }}
    };

Oh, I may have found it! Perhaps the "regInfo()" function is what it does for me.. tell me if I'm wrong.

I also noticed that every time that if you wanted to change the xml file, I should restart wireshark to reconstruct the appropriate arrays of hf field, right?

That's what I was referring to in my comment above:

I'm unsure if this is still a one-time initialization though and if Wireshark has to be restarted if the config file is changed.

I believe a dissector can only initialise the hf entries once, whether they are hard-coded or built dynamically from an external source such as a file.