Webster Pro Control Support

Upgrading from a Webster, WebTrek or WebViewer Control

These three simple steps will upgrade your application from a Webster, WebTrek or WebViewer to a Webster Pro. In a Forms-based application, delete the old control from your form and insert a Webster Pro in its place. You can keep the control ID the same as it was (e.g. Webster1) to minimize code changes. If your application creates the OCX directly (rather than in a design-time form), change the class ID string from “Webster.WebsterCtrl.1” (Webster) or "WebTrek.WebsterCtrl.1" (WebTrek) or "VCIWEBVIEWER.WebsterCtrl.1" (WebViewer) to “Webster.WebsterPro.1”. The DoClickURL event has been removed, so if you handled that event then you will need to move the code from the DoClickURL handler to a BeforeNavigate event handler. Unlike the old DoClickURL event, BeforeNavigate is fired for all navigation actions including container navigation requests (via the Navigate method, assignment to the PageURL property etc.). You can determine whether a BeforeNavigate event is the result of a container action by inspecting the NavContainerAction bit in the event’s NavFlags argument. The archaic LoadComplete event has been removed. It had been fired when the text of a page was all in. Any code in a LoadComplete event handler should be moved to the PageStatusChange event handler. The PageStatusChange is called for status conditions other than text load completion or failure. To trap only that subset of conditions which originally triggered LoadComplete, test for the Status argument indicating a text load completion or failure (PageIsLoaded, LoadingImages, PageLoadFailed or PageLoadCanceled). All other original properties, methods and events are unchanged and require no code modification. Many new and useful API elements have been added but they may be safely ignored if desired.

Switching from a WebTrek Pro Control

The last WebTrek Pro control is forward-compatible with the current Webster Pro release, so switching between them is just a matter of updating the GUIDs and license info. In a Forms-based application, delete the WebTrek Pro from your form and insert a Webster Pro in its place. If you keep the control ID the same as it was (e.g. WebTrekCtrl1) then you will not need to change any code. If your application creates the OCX directly (rather than in a design-time form), change the class ID string from "WebTrek.WebsterCtrlPro.1" to "Webster.WebsterPro.1" for a D-Type control, or HomePageSW.WebsterPro.3 for an S-Type control.