How to update the List Box Field when its value has been changed with another callback function

There is no bug here. 

The original problem is caused by the use of remd(). There are two problems - one is that the return value of remd() is not being used - and whilst a destructive removal of an entry in a list is OK, if you remove the first entry in a list this way, it does not change the list contents, but instead returns a pointer to the new beginning of the list. For example:

lst='(1 2 3 4 5)
remd(2 lst) => (1 3 4 5)
lst => (1 3 4 5)

remd(1 lst) => (3 4 5)
lst => (1 3 4 5)

The reason for this is that the variable lst is pointing to the list cell containing 1 - and the remd() function has no idea what variables are pointing to the same list - all it can do is destructively remove entries within the list, and if it's the first, change what it returns the pointer to. So this is to be expected.

As Lawrence said, you should use the return value of remd.

However, a second issue is that using remd() interferes with the form - you're manipulating data that is used within the form, and what happens is that the selection itself doesn't notice the removal - because you removed it from the list on the form itself. This is just a side effect of using destructive operations on a list that is shared with the form - and so you're getting odd behaviour. Luckily it's easily solved - either use remove() instead of remd(), or continue to use remd() (using the return value as Lawrence suggested) but do it on a copy of the original list:

procedure(fFilterButtonCB(form)
let(
(
    DeSelPinKeyWordList ;list of key words for deselected pin
    pinNameList ;an operation list
);local variable
    DeSelPinKeyWordList = parseString(SISpinInfoSelForm->fDeSelPinKeyWord->value)

    pinNameList = copy(form->fPinInfoSel->value)

    foreach(DeSelPinKeyWord DeSelPinKeyWordList
        foreach(pinName pinNameList
            when(rexMatchp(DeSelPinKeyWord pinName)
                pinNameList=remd(pinName pinNameList)
            );when
        );foreach pinName
    );foreach

    form->fPinInfoSel->value = pinNameList

);let
);proc

As for the final issue with the loop, that's to be expected too.

For a start, the code should be this:

foreach(pinInfoString pinInfoStringList

  FORM1->fPinInfoSel->value = list(pinInfoString)

  printf("%s\n", pinInfoString)

);foreach

Once this is run, the UI only updates at the end - the code is still running and so you won't see the form refresh. So I'm not really sure what you're expecting it to do.

So I'm not sure what long-standing issue Sjoerd was referring to - there's nothing wrong here.

Regards,

Andrew.

There is no bug here. 

The original problem is caused by the use of remd(). There are two problems - one is that the return value of remd() is not being used - and whilst a destructive removal of an entry in a list is OK, if you remove the first entry in a list this way, it does not change the list contents, but instead returns a pointer to the new beginning of the list. For example:

lst='(1 2 3 4 5)
remd(2 lst) => (1 3 4 5)
lst => (1 3 4 5)

remd(1 lst) => (3 4 5)
lst => (1 3 4 5)

The reason for this is that the variable lst is pointing to the list cell containing 1 - and the remd() function has no idea what variables are pointing to the same list - all it can do is destructively remove entries within the list, and if it's the first, change what it returns the pointer to. So this is to be expected.

As Lawrence said, you should use the return value of remd.

However, a second issue is that using remd() interferes with the form - you're manipulating data that is used within the form, and what happens is that the selection itself doesn't notice the removal - because you removed it from the list on the form itself. This is just a side effect of using destructive operations on a list that is shared with the form - and so you're getting odd behaviour. Luckily it's easily solved - either use remove() instead of remd(), or continue to use remd() (using the return value as Lawrence suggested) but do it on a copy of the original list:

procedure(fFilterButtonCB(form)
let(
(
    DeSelPinKeyWordList ;list of key words for deselected pin
    pinNameList ;an operation list
);local variable
    DeSelPinKeyWordList = parseString(SISpinInfoSelForm->fDeSelPinKeyWord->value)

    pinNameList = copy(form->fPinInfoSel->value)

    foreach(DeSelPinKeyWord DeSelPinKeyWordList
        foreach(pinName pinNameList
            when(rexMatchp(DeSelPinKeyWord pinName)
                pinNameList=remd(pinName pinNameList)
            );when
        );foreach pinName
    );foreach

    form->fPinInfoSel->value = pinNameList

);let
);proc

As for the final issue with the loop, that's to be expected too.

For a start, the code should be this:

foreach(pinInfoString pinInfoStringList

  FORM1->fPinInfoSel->value = list(pinInfoString)

  printf("%s\n", pinInfoString)

);foreach

Once this is run, the UI only updates at the end - the code is still running and so you won't see the form refresh. So I'm not really sure what you're expecting it to do.

So I'm not sure what long-standing issue Sjoerd was referring to - there's nothing wrong here.

Regards,

Andrew.