6.5 FormAPI - clearing error state

Adam Stoller · 2005-03-08T15:12:22+00:00

EnvironmentTS 6.5 Solaris 9CCPro ScenarioI've got a DCT with a text-field/browse button for selecting a file -- pretty basic stuff.I have an onChange handler for that text-field which does a callServer() to a very simplistic CGI script that checks to see if the path/file in the text field actually exists on the server and…

Adam Stoller

Environment

Scenario

Either required fields have not been filled out or fields contain invalid values. Please fix this before saving.

Problem

Now - I go back to the text field and remove the extraneous character and hit Tab again - the highlighting around the field goes away - everything looks good except I still have that message at the bottom of the Edit DCR window. The callback code looks basically like this:function callback(val){
var subnav = IWDatacapture.getItem("/subnav");
var status = subnav.isValid();
if (val == 0){
alert("Selected sub-navigation bubble does not appear to exist." +
" Erase or replace.");
subnav.setFocus();
showInvalid(subnav);
}
else {
showValid(subnav);
if(status == false){
IWDatacapture.setHighlightMode(false);
IWDatacapture.redraw();
}
if (validateOutlineLevels() && validateDates("Event")){
if (button_status == IWDatacapture.SAVE_BUTTON ||
button_status == IWDatacapture.SAVECLOSE_BUTTON)
{
IWDatacapture.save();
}
return true;
}
}
return false;
}In the bolded section above I've tried a number of different things:

IWDatacapture.setHightlightMode(true);
IWDatacapture.setHightlightMode(false);
IWDatacapture.redraw();
IWDatacapture.redrawLabels();

Either I managed to miss the right combination of the above calls - or I'm missing the correct call to make to get rid of that annoying message which is no longer applicable. (Note: I have verified that it's going into that conditional code - the logic is fine - the functionality is what's not working)

Anyone else run into this?
Anyone see what I'm missing?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Find more posts tagged with

Comments

Migrateduser

Your code looks just fine and I've seen this in previous versions, too.
<sarcastic_comment>
Nice to see they've addressed this issue.
</sarcastic_comment>
What happens when you focus on another field after you've corrected the browse field? My notion is that the FormAPI will accept it then.

Dave

Current Environment(s):
(1) TS 6.1 SP2 on W2K3
(2) TS 6.1 SP2 on W2K

Adam Stoller

Moving the focus to other fields has no effect on that banner at the bottom -- the specific field in question is un-highlighted when I fix the path (that part works fine) it's just some sort of error handling residue that seems to be left behind that I don't seem to be able to get rid of.

Perhaps the attached will help clarify?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

Yeah, I see what you mean and that's pretty maddening. So, we know for certain that your callback() function is returning true and from the word doc, we know that it's redrawing properly and that the form SHOULD be validating. Hmm...

Like I said, I've experienced very similar things in 6.1, but in my case, focusing on another field seems to "fix" it. I wonder if it would help to put some redundant code in there. For instance, you're retrieving the subnav value but what if you were to do a setValue after you've validated the field? I know, it's redundant, but maybe that's the trigger it needs?

Dave

Current Environment(s):
(1) TS 6.1 SP2 on W2K3
(2) TS 6.1 SP2 on W2K

Adam Stoller

Okay - I've narrowed this down to the point at which I'm convinced it is a bug in the product.

Create a very simple DCT: <?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE datacapture SYSTEM "datacapture5.0.dtd">
<data-capture-requirements type="content">
<ruleset name="article">
<item name="Title">
<text size="55" required="t"/>
</item>
<item name="Subtitle">
<text size="55"/>
</item>
</ruleset>
</data-capture-requirements>

Create a New Form - it will come up with two empty text fields.
Click on Save the Title field becomes highlighted as having a problem and the banner shows up on the bottom as previously mentioned.
Type some text into the Title field and hit the Tab key
The Title field is no longer highlighted as being a problem but the banner remains indicating something is wrong.

This is without any FormAPI code - not even any validation-regex specifications - just a "required" field.

I'll log a case with Support.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

Good idea -- I've seen the same thing, but I'm curious though... would you see a different result if you were to CLICK to the next field rather than tabbing over to it? Even if so, this is definitely a bug.

Dave

Current Environment(s):
(1) TS 6.1 SP2 on W2K3
(2) TS 6.1 SP2 on W2K

Adam Stoller

clicking with the mouse to another field instead of tabbing does not seem to have any effect.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

SandeepMadan

The reason for the Mouse Click event not activating the form validation, is that in Javascript terms, the trace of a key board event i.e onFocus() is not tracked by mouse Events. It may seems to be a bit non relevant but the core reason should be this.

Regards,
Sandeep

Regards,
Sandeep Madan

aggregate N (copy).rptdesign