Extra Attribute within tag Markup to Codebehind

[luizhp]

Hi Guys,

Any ideas how to convert the attribute SortData at Markup to Codebehind ? thanks

MARKUP
<ext:Button ID="btnFindToolOrderName"
   SortData="={{property:'ds_name',direction:'ASC'}}" />

CODEBEHIND
 new ext.Button() {
      Id = "btnFindToolOrderName"
      sortData ?????
  }

[Daniil]

Hi @luizhp,

If you define a non-existing property (there is no the SortData property in the Button class) in markup, it is treated as a shorthand for CustomConfig.

In code behind you should create a ConfigItem and put it to a Button's CustomConfig.

[luizhp]

Hi @luizhp,

If you define a non-existing property (there is no the SortData property in the Button class) in markup, it is treated as a shorthand for CustomConfig.

In code behind you should create a ConfigItem and put it to a Button's CustomConfig.

Thanks for the explanation!!! But in markup, using non-properties, keeps you showing in Visual Studio: "Attribute 'SortData' is not a valid attribute of element 'Button'." It's pretty annoying. So in this moment, I'll continue using the markup but changing with this:

<ext:Button ID="btnFindToolOrderName" runat="server">
   <CustomConfig>
       <ext:ConfigItem Name="SortData" Value="={{property:'id',direction:'ASC'}}"
           Mode="Raw">
       </ext:ConfigItem>
   </CustomConfig>
</ext:Button>

[Daniil]

I don't have such a warning in VS 2012. Though, it might actually happen in previous versions.