Run client event AFTER question event runs - Data Springs Inc. - DotNetNuke Modules - DotNetNuke Module Product Forums - Product Discussion - DotNetNuke Modules

Run client event AFTER question event runs

Last Post 05-11-2012 07:18 PM by Mark Buelsing. 2 Replies.

Author

Messages

Mark Buelsing User is Offline

river guide
Posts:241
Avatar

05-11-2012 01:18 PM
Is there a way to ensure a client side event is fired only after the result of a question event is returned? My question event calls a stored procedure to calculate a value and the client side event grabs the returned value and splits it into pieces and places the pieces into nearby text boxes. I want to be sure the question event is finished returning its answer before the client side event tries to run. I tried having a second question event fire after the first one. And it would set the value on a check box that had the client side event there. But that didn't work either. Thanks for your ideas.

Mark Buelsing User is Offline

river guide
Posts:241
Avatar

05-11-2012 06:37 PM
I have noticed that the process is acting differently depending on the userid that is logged in. For one account, the question event fires, does its calc and returns a value and the initial javascript grabs the returned value and divides it into its pieces and puts the values in the text boxes. Just like I want it to. But for another userid, no values appear in the text boxes. But I can tell that the question event has run and that a value was returned because I can see the result in a text box. Perhaps either the QE is taking longer on one account versus another or perhaps the initial javascript fails on one account and not the other. I can't tell why it is different. But I need a way to ensure the QE runs first and the initial javascript afterwards.

Mark Buelsing User is Offline

river guide
Posts:241
Avatar

05-11-2012 07:18 PM
I realize my first post was talking about the client side event and the second one is talking about the initial javascript. The same javascript is placed in both places. I have come to believe that the client side event is being processed first, right when the user clicks the combo box, and then the QE starts, returns a value and initiates a screen refresh and it is unclear whether the refresh finishes before or after the initial javascript runs.