TagField does not use InputField and DisplayField

[rtic]

(Running on 4.2)

Hello,

since hours I tried to figure out how the TagField gives mit the correct values. I found a workaround, but for me, it's not clear what is happening here.

Here I create the TagField:

 var conf = new EX.TagField.Config()
            {
                AutoLoadOnValue = true,
                Height = 50,
                MaxHeight = 150,
                DisplayField = "Bez",
                ValueField = "Id", // ext.js InputField?
            };
 _tagField = new EX.TagField(conf)
            {
                ID = _intnameParent + "$tf$" + _control_config.Intname,
            };

        and....

  _tagField.Listeners.BeforeRender.Fn =
               $@"
                    function(evt,elm)
                    {{
                        Debug.Log('=> ' + this.displayField + ' ' + this.inputField);
                    }}";

Log result:

    displayField == "text"
    inputField == undefined

In my understanding, both fields must be set.

when I do:

 _tagField.Listeners.BeforeRender.Fn =
               $@"
                    function(evt,elm)
                    {{
                        this.displayField = 'Bez';
                        this.inputField = 'Id';
                    }}";

It works pretty. So ext.js do the right thing, but Ext.Net feed the wrong data? I'm a little bit confused about this.

To explain the szenario (and why I can't write a reproducing source)

I've a dynamic created form with a GridInside. The TagField runs as component within a ComponentColumn inside the grid and the grids store is feeded with complex structured data.

I'm also confused why there is not InputField Property in the TagField CLASS. With the hack the correct data is shown. So ext.js can do the job, but this can't be the solution.

[fabricio.murta]

Hello @rtic! Welcome to Ext.NET forums!

I'm afraid we can do little to help you without understanding and being able to reproduce the issue. You already stated you couldn't come up with a test case to reproduce it, but yet your description really leaves a lot of room for uncertainty on how you would be using the feature.

That said, I can just point you to some threads that may help you coming up with runnable test cases. Maybe if you read thru them, you'll find a way to gather it up in a runnable code sample so that we can jump in and help you make it work (or fix if that's a bug in Ext.NET).

Here's the literature:
- More Information Required (nice test case templates within!)
- Forum Guidelines For Posting New Topics (do's and don'ts when posting threads, useful read!)
- Tips for creating simplified code samples (pro tips on getting your proprietary and complex code into neat generic, Ext.NET-focused test cases.

Well, I hope this helps!

[rtic]

So let me ask simpler:

Ext.Net does not define the Property InputField, what must be done in Ext.Net to set this field or is it not suppsorted. My code walk shows that this "could" be the main problem for ext.js not working.

[fabricio.murta]

Hello @rtic!

Ext.NET's tagfield does not define any InputField property or config option, but I don't see this thru its inheritance path in ExtJS documentation as well so... I'm still not getting the point here.

I don't have any guesses on what could be the problem with the information you provided.