Tutorial User Guide > Drive Pages > Drive Page Philosophy
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">   
Drive Page Philosophy
Drive pages should contain enough information to show the logical flow from one dialog to the next.
In general, avoid making calls to AAI.next_dialog() from within PCL functions. The reason for this is that following the logic flow of <dialog> tags will become difficult if logic operations are hidden within PCL functions and not visible on the drive pages.
Make use of the available <dialog> tag attributes quedlg, errordlg and the <returnerror> elements on drive pages, so that a reader can follow the logic scenario. Calls to AAI.next_dialog listed on HREF hypertext links also enable following logic scenarios on drive pages.
Finally, use of blank line spacing and <!-- comment statements --> can help delineate logic blocks on drive pages.