Pedantic observation from a NEWBIE :-)

[Darren Neimke]

I'm just starting to develop InfoPath forms (for fun or profit) and, after
browsing through SDK documentation thought that I'd dive in and see how some
of the Sample Forms are implemented to get ideas about how to build "best
practices" forms.

So, I opened up the Detailed TimeCard form and - being a true programmer
- opened up the js code file in WSE.

Looking at the OnAfterChange handlers you can see that, changes cause calls
through to updateTotals(). There's some code in there which causes the
OnAfterChange handlers to exit if (XDocument.IsSigned) or if
(oEvent.IsUndoRedo).

Shouldn't they also exit if (oEvent.Operation == "Delete"). That's what
you'd normally do right?

 

[Andrew Watt [MVP - InfoPath]]

I'm just starting to develop InfoPath forms (for fun or profit) and, after
browsing through SDK documentation thought that I'd dive in and see how some
of the Sample Forms are implemented to get ideas about how to build "best
practices" forms.

So, I opened up the Detailed TimeCard form and - being a true programmer
- opened up the js code file in WSE.

Looking at the OnAfterChange handlers you can see that, changes cause calls
through to updateTotals(). There's some code in there which causes the
OnAfterChange handlers to exit if (XDocument.IsSigned) or if
(oEvent.IsUndoRedo).

Shouldn't they also exit if (oEvent.Operation == "Delete"). That's what
you'd normally do right?

Hi Darren,

I haven't gone to the sample form templates to check the exact
scenario, but if the form control had held a value and that was later
deleted wouldn't you want to reflect the effect of the deletion in the
total?

Andrew Watt
MVP - InfoPath

 

[Darren Neimke]

Yes, well... I guess that you've got a point there don't you