Thanks for the advice. I am looking into everything right now. My callLater attempt failed, so now I am going to have to get really clever...which I'm not LOL. Starting with a raw Click Event is going to be a much less elegant solution, because if you listen for a click on the grid, you then have to test if you clicked a row, if you clicked the radio button, or if you simply clicked the datagrid header before you can decide what data to retrieve and what things have changed and whether you want to dispatch a custom event. I was hoping for a much simpler and cleaner solution.
You mentioned about stopping propogation of the click event, but I have no idea how the whole selectionChange event gets propogated. I just know that a click makes the whole thing start obviously, but I don't know where you would go about interupting the whole selectionChange event, and I am not sure that I really would want to. Visual changes happen in my program based on the radioButton and the items selected in the dataGrid, so I am not sure that I would want to interupt the selection process. -- View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Listen-for-the-Originator-of-an-Event-tp14290p14296.html Sent from the Apache Flex Users mailing list archive at Nabble.com.
