Part IV: Controlling the Behavior of the Browser in .NET

Painting QR Code JIS X 0510 in .NET Part IV: Controlling the Behavior of the Browser

To advance through the screens automatically, click the Start Slide Show button Control the speed at which the slide show displays the screens by clicking the Slow, Medium, or Fast button Click the Stop button to halt the slide show You can then continue manually with the Forward and Back buttons or turn the slide show back on with the Start Slide Show button The larger you make the Screen Viewer window, the better the screen shots look Click the window s Maximize button to increase the viewer to its largest size in order to view the screen shots at their best (see Figure 19-4) When you re finished with the Screen Viewer, you can just close the window and then also close the Screen Spy dialog box If you leave the Capture Screens option selected, the browser continues to add new screen shots to the ones that already exist If you want to start fresh, click the Delete Screens button in the Screen Spy dialog box The program then deletes all screens that currently exist If the Capture Screens option is selected, the browser goes back to capturing screens Each screen shot s filename includes the date and time the capture was taken This filename appears at the top of the Screen Viewer window, making it easy for you to know what was happening with the browser at any given time

20

Understanding the editor Discovering the seven script attribute groups Exploring the default script file Examining a complete script file Understanding the attributes in each script group

he Browser Construction Kit editor doesn t actually create a browser Your browser is created by a compiler that reads a script file, creating the browser with the components and options you selected The truth is that, although it s a convenient program, you don t even need the browser editor You can create your browser script file by hand I don t suggest doing this, though, because one tiny mistake could make your browser unusable But whether you want to experiment with a browser script file or not, you may want to know more about how it works That s what you discover in this chapter

The Browser Construction Kit s editor is nothing more than a handy way to create a browser script file The editor keeps track of everything you add to your custom browser, and, when you save your work, takes that information and creates the browser script file Another advantage of the editor is that you can see the results of your settings right away, without having to first compile the browser The editor and the script file do share one important characteristic: the way the different browser settings are organized As you probably know, the browser editor organizes your browser settings into seven groups (shown in Figure 20-1), each of which is accessed from the list box below the toolbox buttons The resultant script file, too, is organized into these seven groups

Each group of settings starts with a title enclosed in square brackets The groups are also organized into a specific order, and both the editor (when you try to reload a browser in progress) and the compiler (when you try to compile your browser) expect everything to be exactly in this order: Window Attributes, Browser Attributes, Toolbar Attributes, Status Bar Attributes, Menu Bar Attributes, Function Attributes, and Address Bar Attributes Here s what a browser script file looks like, with the details of each section replaced with vertical ellipses:

[WINDOW ATTRIBUTES] [BROWSER ATTRIBUTES]

[TOOLBAR ATTRIBUTES] [STATUS BAR ATTRIBUTES] [MENU BAR ATTRIBUTES] [FUNCTION ATTRIBUTES] [ADDRESS BAR ATTRIBUTES]