Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ext.Net.Node implements non-existing listeners #1615

fabriciomurta opened this Issue Oct 10, 2018 · 1 comment


None yet
1 participant
Copy link

fabriciomurta commented Oct 10, 2018

Found: 4.7.1
Ext.NET forum thread: NodeExpand not fire

This is most likely a left over, and likely from Ext.NET 1! The tree panel's nodes are instances of which, in turn, are an instance of decorated by, which do not implement the nodeexpand nor nodecollapse events; instead, it does have the expand and collapse events, respectively.

Notwithstanding, the latter events are not properly set up to the "decorated" node, but stay within the definition, so the events never get fired. This part could be understood as an issue with Ext JS.

Then effectively, in the current state of Ext.NET, it is not possible to bind events directly to specific tree nodes. This is probably also a left over from the Ext JS side, from version 3 series.

So this issue could be seen as a two-part issue:

  1. Fix the C# mappings of the listeners from Ext.NET side
  2. Fix the actual setup of listeners when defined within individual nodes.

This comment has been minimized.

Copy link
Contributor Author

fabriciomurta commented Feb 22, 2019

By design, listeners on nodes can't be defined as config options (before render), as the nodes are not really observable components, but data. Binding the documented events from is only supported at run time, for example, using .on() in the specific node.

To specify listeners at definition-time, it is necessary to use the tree panel's "item*" events.

So, by design, listeners won't be supported in individual nodes; that's an Ext JS limitation.

@fabriciomurta fabriciomurta removed this from the 4.7.2 milestone Feb 22, 2019

@fabriciomurta fabriciomurta added this to the 4.8.0 milestone Feb 22, 2019

@fabriciomurta fabriciomurta self-assigned this Feb 22, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.