Skip to Content
avatar image
Former Member

Extended Value Selector- Problem update

Hi,

We have an interface that contains two input fields that use the Extended Value Selector widget. One of the fields is dependent on the other i.e. when the field's value changes the possible values of the other are also updated.

Our problem is that the possible values of the second field are not updated when the user presses tab to get to the next field. When the user opens the extended value selector for the first time the values are not up to date. However, on the second attempt the values are correct.

It seems that the correct values are loaded, but not shown in the Widget. Does anyone know of a possible solution/workaround?

Cheers,

Jens

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Nov 02, 2007 at 01:53 PM

    Hi Jens,

    Ideally, you populate the second field's EVS values on an "action". And unfortunately pressing tab or focusing on the field does not generate an event and hence they are not populated.

    What's happening in your case is, when the user opens the second EVS, framework generates an auto event and a server round trip and then the values get populated for the second time.

    As you say both the fields are input fields, make the user press enter in the first field and onEnter of this field, populate field2's EVS values.

    Hope that helps.

    Cheers,

    Rajit

    Message was edited by:

    Rajit Srinivas

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Ayyapparaj,

      the log entries show that everything in the backend is correct, only what is shown is wrong and inconsistant with these logs.

      Cheers,

      Jens