Re: [flexcoders] Tree click vs change
Thanks. This worked well. On Fri, Jul 2, 2010 at 2:43 PM, Alex Harui wrote: > > > Add a high priority mouseDown handler and record the selectedIndex then. > > > > On 7/2/10 2:34 PM, "Richard Rodseth" wrote: > > > > > > > We have a datagrid that gets updated when the user clicks a node in a tree > (or moves through it using arrow keys). > We're handling the change event in the tree to issue the update request. > A request has come in that clicking an already selected node should do a > refresh. > > We tried having both change and click handlers, where the click handler > would check if the selection was unchanged. But that didn't work because the > change event fires first so the selection reported a click time is always > the same. > > Any suggestions? > > > > > > -- > Alex Harui > Flex SDK Team > Adobe System, Inc. > http://blogs.adobe.com/aharui > >
Re: [flexcoders] Tree click vs change
Add a high priority mouseDown handler and record the selectedIndex then. On 7/2/10 2:34 PM, "Richard Rodseth" wrote: We have a datagrid that gets updated when the user clicks a node in a tree (or moves through it using arrow keys). We're handling the change event in the tree to issue the update request. A request has come in that clicking an already selected node should do a refresh. We tried having both change and click handlers, where the click handler would check if the selection was unchanged. But that didn't work because the change event fires first so the selection reported a click time is always the same. Any suggestions? -- Alex Harui Flex SDK Team Adobe System, Inc. http://blogs.adobe.com/aharui
[flexcoders] Tree click vs change
We have a datagrid that gets updated when the user clicks a node in a tree (or moves through it using arrow keys). We're handling the change event in the tree to issue the update request. A request has come in that clicking an already selected node should do a refresh. We tried having both change and click handlers, where the click handler would check if the selection was unchanged. But that didn't work because the change event fires first so the selection reported a click time is always the same. Any suggestions?
