You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Plugins like the Badge, CellEditing, RowEditing and CellDragDrop all intherit from Ext.Net.Plugin which ultimately inherits from WebControls.
WebControls in turn registers a property called Enabled. This suggests that giving to any plugin the Enabled="false" property will effectively disable the plugin, what does not happen at all.
It is possible to reproduce with at least the Badge and CellDragDrop plugins in a TableView, but potentially happens with all and any plug ins Ext.NET supports.
It is necessary either to hide this property (as it is not supported at all) or create an appropriate handling for every plugIn.
A possible candidate if handling would be the Ext.Net.Plugins class having a generic handler, emitting enabled : <true/false> to JavaScript depending on the setting. Specific plugins might require specific behavior depending on the Enabled state.
Plugins like the Badge, CellEditing, RowEditing and CellDragDrop all intherit from
Ext.Net.Plugin
which ultimately inherits fromWebControls
.WebControls
in turn registers a property calledEnabled
. This suggests that giving to any plugin theEnabled="false"
property will effectively disable the plugin, what does not happen at all.It is possible to reproduce with at least the
Badge
andCellDragDrop
plugins in aTableView
, but potentially happens with all and any plug ins Ext.NET supports.It is necessary either to hide this property (as it is not supported at all) or create an appropriate handling for every plugIn.
A possible candidate if handling would be the
Ext.Net.Plugins
class having a generic handler, emittingenabled : <true/false>
to JavaScript depending on the setting. Specific plugins might require specific behavior depending on theEnabled
state.Related forum issue: CelllDragDrop should override Enable property
The text was updated successfully, but these errors were encountered: