<choice /> event handler?

I have a need to perform an action when a user selects a choice on a DCT which implements the <choice /> DCT control.

I see that as far as FormAPI is concerned the choice element does in fact exist as 'choice' when addressing an item for example.

Example. item/choice/item 1 or item 2

BUT I cant for the life of me figure out how to use the event registry to do something when a user makes a choice.

OnReplicantAdded etc... does not seem to work. Any advice on this is appreciated.

Thanks,

Tim

Find more posts tagged with

Comments

ISCBorisB

I have a need to perform an action when a user selects a choice on a DCT which implements the <choice /> DCT control.

I see that as far as FormAPI is concerned the choice element does in fact exist as 'choice' when addressing an item for example.

Example. item/choice/item 1 or item 2

BUT I cant for the life of me figure out how to use the event registry to do something when a user makes a choice.

OnReplicantAdded etc... does not seem to work. Any advice on this is appreciated.

Thanks,

Tim

I've looked into it some time ago, was not able to find anything either.

Choice Control Type (IWItem.getType) is 'orcontainer' all right. Problem is, it *seems* to be "Or Container"
with number of Replicants fixed to one. Thus, Replicant Events do not Fire (if you can neither add nor move a
Replicant, well...). An exception (at least in 6.7) was useless 'OnReplicantDelete'. It fired upon clicking
greyed out(!) Container's - and sure enough did not delete anything.

Tim__D

I've looked into it some time ago, was not able to find anything either.

Choice Control Type (IWItem.getType) is 'orcontainer' all right. Problem is, it *seems* to be "Or Container"
with number of Replicants fixed to one. Thus, Replicant Events do not Fire (if you can neither add nor move a
Replicant, well...). An exception (at least in 6.7) was useless 'OnReplicantDelete'. It fired upon clicking
greyed out(!) Container's - and sure enough did not delete anything.

Thanks for your thoughts on this.

I'm going to try a container with no location as another element and see if that helps. I suspect that if I set the min and max to 1 it wont operate as a choice after the fact but Smiley Happy

if I set it to 2 I may be able to do what I want with some trickery Smiley Wink

Tim__D

Ok so I realize that this may only come in handy under very special circumstances but here goes....

Example:
I have a DCT which due to some new requirements needs to implement callServer() vs <inline /> to populate some fields which provide dynamic options for selection sourced from a database. There are several sets of fields all within their own named containers which do not repeat. These containers are then within a <choice /> element. Now in the past with the <inline/> approach users could use the choice element to choose which field set to populate no problem but when doing this all through callServer it became necessary to register events when another "choice" was made to populate the dynamic options for user selection which are different per choice.

Basically here is how its done if you have no other option...

Replace the choice element with this.


<container name="whatever" min="1" max="2" combination="or">

Note the lack of location and a max of 2 not 1. Use of location would not mimic the choice element which has no location AND if you set max to 1 you cant register events on a container either Smiley Happy

. So we use 2 instead to get our events and FormAPI after that to get the behavior we want.

In addition to your normal event handler register an additional one.


..................../type","OnReplicantAdded",makeChoice,false);

Finally include this little jem.


function makeChoice(objItem) {
    var objParent = IWDatacapture.getItem(objItem.getName() + "/../type");
    setTimeout(function(){objParent.deleteInstance(1)},0);
}

and yes..even though the timeout is 0 it does not work without it.

Again, this is a very limited use case but since its the best answer to the question I've got, I figured I'd post it.

Cheers,

Tim