Hi Everyone
Thanks a lot for the ideas. I think what I'm going
to end up doing is store everything in a session
variable, and pass the next fuseaction in a hidden
field.
I have a javascript function that appears on every
page.
function onTabClick(xfa) {
window.location.href = 'index.cfm?fuseaction=' + xfa;
}
On pages that have to submit a form before
relocating, I "override" that function by creating
another version of it, such as:
function onTabClick(xfa) {
frm = document.forms.myForm;
frm.nextXFA.value = xfa;
frm.submit();
}
Then I have
<cflocation url="index.cfm?fuseaction=#attributes.nextXFA#">
at the end of the fuseaction that takes the form submit.
I was hoping to come up with something a little simpler,
but I'm forced to deal with the fact that each tab could
potentially handle the onTabClick event a little
differently.
The dHTML layers suggestion would be perfect, and I may
revisit that one if I can figure out how to do so without
making maintenance more difficult.
Patrick
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
