How to use hiHighlightField() to highlight a particular field if the input is incorrect

Hi Manikandan,

Take a look at my code example in this post which shows the use of the hiHighlightField() function.

Hopefully this will help you,

Regards,

Lawrence.

Hi Lawrence,

                Thanks for the help. I implemented the 'hiHighlightField()' in a way similar to that in the example which you gave me. Even after that i am getting the following error. I am attaching the snippet of the code i wrote:-

*Error* eval: not a function - 'cellL
*Error* car: Can't take car of atom - ERROR

CODE SNIPPET:-

t_libL   = r_Form->TabField->page1->libraryL->value

t_cellL = r_Form->TabField->page1->cellL->value

if( ddGetObj( t_libL t_cellL ) then

  hiHighlightField(r_Form 'cellL 0)

else

  hiHighlightField(r_Form 'cellL 1)

) ; if

Thanks and Regards,

Manikandan Kuzandhaivelu

Manikandan, can you email me the entire code? I can't see why it should give this error as there's nothing in your snippet which should suggest that. I do think that your calls to hiHighlightField should have rForm->TabField->page1 as the first argument rather than rForm, but wouldn't expect (without trying it) that this would lead to that error. Kind Regards (and apologies for not answering last week as I had a busy work week and was away), Andrew

For anyone interested in the problem...

From having seen the whole code, the issue was not with hiHighlightField() at all, but in the specification of the ?modifyCallback. The expectation is that ?modifyCallback is the name of the function, not a complete expression - and "hi" will add the arguments to the function call itself. If you specify a complete expression, the arguments will still be added, but these arguments will end up being seen as a second function call, with the name of the function being the quoted field name - hence the error.

Unfortunately this shows that seeing the whole code is often important to understand bugs - they're not always where you might think they are...

Regards,

Andrew.

I want to dynamically trigger the addition of new fields in a MultiTab GUI through hiAddFields() SKILL command. How should i give the Form name argument in this case since i want one of the Tab to get updated?duvet sets uk

You can provide like this 

hiAddFields(YourForm->TabFieldName->page l_FieldsToBeAdded)

w.r.t to the snippet i gave above, it can be coded as

hiAddFields(r_Form->TabField->page1 l_FieldsToBeAdded)

where 'TabField' is the tabField I created inside the Form r_Form

Thanks and Regards,

Manikandan Kuzandhaivelu

Manikandan,

The post to which you replied is a thinly disguised spam post (they've clearly just taken some text from elsewhere and posted them onto some other vaguely relevant thread, with a link to promote sales of a product). So these posts are being deleted...

Andrew.