CGDevTools Forum

I'm sure this is really simple, but the answer is eluding me. I'm using OnBeforeStepChanging in the CGJQWizard to validate a user's entries and if they're not OK, I want to stop them moving to the next step. How do I do that?

Hello,

Please use the OnStepChanging event...and there, you can decide if going to next/prev:

Code: Select all

IWCGJQWizard1.Next;

Code: Select all

IWCGJQWizard1.Previous;

To get the direction:

Code: Select all

Dir:= AParams.Values['dir'];

To get the new index:

Code: Select all

nextIndex:= StrToInt(AParams.Values['newIndex']);

Best Regards.

Thanks. The "newIndex" (or "currentIndex") paramas don't appear to be included in AParams - although "dir" is. Perhaps I'm doing something wrong. I can get the info from ActiveStep Index of course.

Hi MikeC,

The "newIndex" (or "currentIndex") paramas don't appear to be included in AParams - although "dir" is.

Sorry, my fault...I forgot to mention, you need have SendAllArguments = True:

Code: Select all

IWCGJQWizard1.JQWizardOptions.OnStepChanging.SendAllArguments := True;

Best Regards.

Great, thanks! I do have the same issue as Montse Carver with this Wizard - the event is firing more than once. I understand this is fixed in the next build. Any idea if the date?

Hello,

Already uploaded.

Best Regards.

Does this correspondence suggest that the "OnBeforeStepChanging" is deprecated? How is the event to be used, as I notice it is no longer firing with the recent updates?

Please advise...

Regards,
Monte Carver

Hello,

Nothing was deprecated...but YES, improved:

viewtopic.php?f=147&t=3105#p15492

Use this way...

Best Regards.

Alexander,

I am still not clear. Prior to a recent updated the OnBeforeStepChanging would fire. Now it does not. And I understand the suggestion to use "OnStepChanging". The REAL question is what is difference between OnBefore and Changing. When does one employ the OnBefore? Does one disregard this event moving forward?

Thanks for the clarification.

Monte

Hi MCarver,

I found the problem in jquery plugin..it was design bug...anyway fixed in published beta (3.0.0.101).
Thanks.

Best Regards.