How does eValid handle I-frame and frames within frames and all of that stuff?
Good question KatieF.
The answer is, "very carefully".
As you may know, eValid runs sub-windows as separate windows, not tabs in the same window.
(They really are the same, just how you see them differs).
The base window is always Window zero...zero origin indexing.
Here is a basic eValid command showing the parts, including the frame path: http://www.e-valid.com/Products/Documen ... _path.html
So that eValid's script command interpreter can know what the correct thing to do is, every command carries with it a frame path, if needed.
The nesting of frame paths is by number, to wit:
indicating that the 14th frame is a child of frame 1 and it is [of course] a child of frame 0.
This way, there's zero ambiguity.
-- eValid Support