RAIDAR
The FoxPro Debugger for
DOS and Windows.
"Finds your bugs and kills them dead!"
Performance Dynamics Associates
305 Madison Ave. Suite 1420
New York, NY 10165
1. Introduction
You have just purchased Raidar, the best only full featured development and debugging tool available for FoxPro 2.5 DOS and FoxPros for Windows! This manual will help you in understanding what Raidaris, how it works, and how to use it. It is only through real use that you will begin to understand the many ways that it can be used.
Raidar is actually two products in one. First, it provides you with full debugging support. You can access all FoxPro debugging tools in the middle of a running application without having to quit to the command window. This means that you do not have to quit your application, set up your debugging environment, go back into the program, and return to the spot where you needed debugging help. Raidar does all this and more. You can call Raidar with an ON KEY LABEL call, an ON ERROR routine, or a specific call to Raidar by one of your program modules. When called, Raidar will allow you to open up the debug and trace windows while you are running your application. You will be able to look at code as it runs, set the speed of the trace window, look at complete or selected memory listings, even open the SET VIEW dialog, all while your code is still running.
Raidar not only gives you access to all FoxPro's debugging aids, it can serve as a shell to help you with program development. You can open up an application file and choose any editable file from the scrollable list that you seel. Open and edit the file. It does not matter if it is a program file, screen file, query, report, label or menu. Raidar knows and opens the appropriate design surface for you. Look up the syntax for a command. Look at the open tables, their structure, contents, and indexes, and even run a FoxPro command, while your application is running.
Raidar offers you the unique ability to evaluate what is going on in your application with the possibility of fixing it even while the program is still running. You can save hours of laborious work that, without Raidar , would add days to your production schedule.
Raidar is designed to run in conjunction with your already running application. To do this we have engineered the product so that it will coexist with your applications. This task is not as simple as it seems. It is therefore very important that you have a good understanding of what Raidar is and how it works before you start to use the program. The first part of this manual is a discussion of how Raidar is designed and how to load it with your application. The second half of the manual details the individual functions and how they can be used.
2. What Raidar is and how it works.
Raidar is a FoxPro 2.5 application. 100% of Raidar is FoxPro Code. It does not make any library calls, does not use any 'C' code, and does not go into the internals of FoxPro or DOS in any fashion. The product is distributed to you as an encrypted .APP file that you can call in any fashion that you want from the command window or from a running application.
Raidar is a single .APP file. The application has been coded so that it will run under both FoxPro Windows and FoxPro DOS. In FoxPro Windows it behaves like you would expect a Windows Application to behave. In FoxPro DOS, it behaves as you would expect a FoxPro DOS application to behave.
In theory Raidar is simply a menu that idles as a part of your application. When you call a function from the Raidar menu it launches a Raidar code module that performs the specified activity. The difference between Raidar modules and other code modules in your application is that while the Raidar module is running your application is suspended. When the Raidar module finishes, it cleans up after itself and returns control to the running application. As far as your application is concerned, nothing has happened.
When you first call Raidar , it "loads" itself into memory. While doing this it creates a series of approximately 70 memory variables that it will use. All these memory variables are prefaced with "_cur_" and contain information pertaining to environment conditions that Raidar may affect during its operation. In addition to these variables Raidar also creates an array that it uses to store information about ON KEY LABEL settings. Depending on how you use Raidar , the information in this array may change during operation.
The next to last action that Raidar takes is to look at the captured ON KEY LABEL settings. Depending on your Raidar setup code, it turns off any ON KEY LABEL associated with the left mouse button. Raidar needs this to navigate its menu. If your application uses an ON KEY LABEL on the left mouse button, there will be a certain amount of contention for its use. We will discuss this later.
The last thing that Raidar does before returning control to you application is create its menu. Effective with Raidar Version 2.53 you can install Raidar in two different fashions. This change was made because we discovered an unresolvable conflict between a non-FoxPro System system menu and the Raidar menu. Raidar was reengineered to deal with this conflict.
The two different methods of installing Raidar are as follows:
1. Install Raidar in its own window with its own menu.
2. Install Raidar as a menu pad on the active menu.
Installation preference is determined by an option in the Raidar setup dialog (located on the MODIFY option of the Raidar menu.) The option is titled "Install Raidar as a menu pad when possible."
If this setup option is checked Raidar try to load itself on your menu. The word "try" is key here. Raidar will evaluate your application's environment when you call it and, if there is an active menu, it will install itself as a new pad on that menu. If you have not specified this setup option or if there is no menu present at the moment that you invoke the program, Raidar will install itself in a window with its own menu in most circumstances. If your application is running with a non-FoxPro system menu Raidar will install itself on the menu no matter what your preference. It does this to avoid a death lock conflict between the Raidar menu and your application's menu.
When you change the menu installation preference in Raidar and save your setup, Raidar senses the change and automatically reinstalls Raidar in the selected mode.
When you install Raidar on an active system menu the menu pad appears to the right of the lasts menu pad on the menu. If this pushes the menu off the screen an arrow key appears, indicating that you have more options. Using the right arrow key will take you there. When you install Raidar on a DEFINE MENU mymenu type menu the DOS and Windows behavior differ. In DOS the menu pad appears to the right of the last defined menu pad. In FoxPro for Windows the menu pad appears either to the right or above the last menu pad, depending on the circumstance. This is behavior controlled by FoxPro and we cannot change it, not matter how hard we tried. It may look a little funny, but it works.
If you install Raidar in its own window the menu is active only when the Raidar main debugging window is active. Depending on which option you have chosen (FoxPro DOS only) Raidar sets up the screen for debugging and then returns control to your application. If you are running FoxPro Windows, Raidar returns control to your application with its icon in the lower left-hand corner of the screen. If you are running Raidar installed on your menu, your application runs just as it normally does unless you select an option from the menu.
When you begin Raidar and call one of its options from the main debugging menu the following happens. The menu calls RAIDAR.APP with a parmeter. The dispatch program calls the appropriate sub-program after pushing the menu onto the stack. The sub-program then takes control of the FoxPro, suspending your application. It does what is required and, when it is finished (or when you are finished with it) it closes down, releases any windows or menus that it has created, changes the environmental variables back to your application defaults, and then "goes away." Raidar , when not actively involved in processing one of its commands, does not take any processing power away from your application. The only drain on system resources it the window that it runs in and the menu that controls it.
Raidar does no code processing in the background. Raidar intervenes when called, does what it has to and then leaves. You can leave Raidar active throughout the run of your application and never know that it is there until you need it. When you decide that you do not need Raidar any longer, you can exit back to your application, back to FoxPro, or directly to DOS (FoxPro DOS) or Windows (FoxPro Windows) from the Raidar main debugging menu.
If you are running Raidar in its own window it exists only inside this window (called RAIDAR). All processing that it does goes to that window. It is a floating, minimizable window. You can move it or size it as you wish. In FoxPro for Windows Raidar starts as a minimized icon by default. With FoxPro for DOS you have the option of having Raidar start as a minimized or a full sized window. Depending on the option that you select for 'Set Video Display to Maximum Lines' (also in the Raidar setup screen) the Raidar window will either overlay your running application or occupy the lower half of the expanded screen. Double clicking on the top border of the Raidar window will minimize it. The minimized window is floating and you can "park" it wherever you want on the screen while your application runs. Double clicking on the minimized window reopens the debugger and gives you access to all of Raidar 's services.
If you are running Raidar as a menu pad on your application's menu things are a bit different. Each time you call Raidar it creates its own output window called _DISPLAY. Output is directed there and, upon completion, Raidar releases the window before returning control to your application.
Note: When Raidar starts it collects information, stores the information to a collection of public variables that it creates, creates its menu or adds a set of popups to an existing menu, and then it terminates. After Raidar installs itself it is no longer in the calling stack. The menu is all that remains active. Each of the menu choices calls Raidar with a "DO RAIDAR WITH parameters" call when the user selects an option. This is how Raidar manages to stay out of the way while you run you application.
There is a down side to this architecture. It is important that RAIDAR.APP be visible on the FoxPro Path at all times. There are two options for this. The first is to make sure that directory where RAIDAR.APP is located is included in the application path at all times. The second is to find a way to "hard wire" the location of RAIDAR.APP into the menu. Raidar uses the second approach. When you start Raidar the program checks to make sure that RAIDAR.APP is directly visible. If it is not it will ask you where it is located. It then takes the specified path and uses it when it creates the Raidar menu.
Things can get a bit confusing at times with Raidar running in either mode. Your application has a tendency to "cover up" Raidar's menu from time to time. This is why Raidar has two On Key Labels that it creates when it installs itself.
Raidar sets two On Key Label keys for itself. They are Ctrl+PgUp and Ctrl+PgDn. Depending on which mode Raidar is working in they do different things.
If you are working with Raidar attached to your menu the Ctrl+PgUp key will activate the Raidar Popup. It will activate it even in circumstances where the menu is not visible. You can then select from the menu as you would normally. Under certain circumstances the code attached to this option will do some unexpected things to your menu. We know of one case where the entire system menu shows up in the middle of an open Raidar Window. The menu is not attached to the window so you can move the window down below the menu and actually slide it back up over the menu. (Weird!) When you exit the Raidar task the menu returns to its proper location. If for some reason the menu gets messed up, just reinvoke Raidar. This should straighten things out. If you activate Raidar in this fashion in the middle of a MODAL read, you will find that all the menu options are dimmed. This is as it should be. The moral here is not to use this option unless you really need to.
The Ctrl+PgDn key has no effect when running with Raidar attached to your menu.
If Raidar is installed in its own window the Ctrl+PgUp key will maximize the Raidar window. Ctrl+PgDn will minimize it. This allows you to get at Raidar even when it is hidden behind one of your windows. Depending on your code it is possible that you will have problems keeping Raidar active. If you are using an ON KEY LABEL loop that checks for WONTOP and Raidar is not included in your code, you may find that you cannot keep Raidar active. If this is the case, we recommend installing Raidar on your menu instead of rewriting you application.
3. Starting Raidar
There are three basic methods that we recommend you use in starting Raidar .
A. ON KEY LABEL: Set up an ON KEY LABEL key that calls Raidar . This is the preferred method. Pay particular attention to your PUSH and POP KEY commands when you do this. If you push OKLs onto a stack and CLEAR the current settings, make sure that you reissue the OKL command controlling Raidar after each PUSH KEY CLEAR. The same is true when POPping OKLs off the stack. If you find that there are "dead" spots in your application where Raidar is not available, this is the most likely source of the problem.
B. ON ERROR: You can either call Raidar as your ON ERROR routine or as an option from your error handler. Depending on the situation one method or another has advantages.
C. IN-LINE CODE: Occasionally you might want to invoke Raidar directly from your own application code. We do not recommend this approach, however. We also do not recommend that you put SUSPENDs in your production work either. It is, however, a good tool to uses when debugging particularly difficult pieces of code. It works well together with the SUSPEND command.
Calling Raidar at a client site.
Your developer's license for Raidar gives you the right to temporarily install Raidar on your client's machines for your own use. We recommend that you use the following approach when finishing your code prior to final application production. Go through your code and, wherever there is a line of code that either activates Raidar or sets an OKL that calls Raidar do the following: Surround this line by a conditional IF--ENDIF construct as is done in the following example.
IF getenv('pt_debug') = '1'
ON KEY LABEL ALT+F12 DO Raidar
ENDIF
What this does is to ensure that this line of code will not execute unless there is a DOS environmental variable named PT_DEBUG set up before you start FoxPro and that you have set its value to '1'. (Note: All returns from gearshift() are character strings.) There is minimal overhead when you do this. On a typical machine you can make approximately 10,000 calls to GETENV() in a second. This allows you to debug at a client site while keeping your debugging tools hidden from the end user.
When you call Raidar from an .EXE file you must make sure that RAIDAR is visible to the .EXE file. The best way to ensure this is to place Raidar in the same directory as the application. This way there will be no path problems. If this is not acceptable you must make sure that your application includes the directory where RAIDAR is placed in the application's SET PATH statement.
There are several Raidar options that are not available to you when you are running an .EXE file in the standalone mode. These are:
1. The Debug window
2. The Trace window
3. The Set View window
4. Access to FoxPro help
5. Modify Screen, Menu, Query, Report, and Label design surfaces.
These services are not supported by the FoxPro runtime support libraries. If you are running your .EXE file inside of FoxPro (which is possible) the above services are available as normal.
4. Raidar General Characteristics.
Raidar
will run on any computer that will run FoxPro 2.5 for DOS or FoxPro Windows. Raidar is designed to use minimal system resources but, like all applications, it does use some memory. Raidar creates approximately 70 PUBLIC memory variables that persist until Raidar is terminated. It also creates three arrays that, depending on the ON KEY LABELS and menu and screen files that are associated with our application, may become quite large. You may encounter problems with number of memory variables. If this happens, change your MVCOUNT to accommodate Raidar .Like most other FoxPro applications, Raidar uses the FoxPro READ in many areas. If your application is at Read Level 5 many of Raidar's capabilities will not be open to you. You need not worry about crashing your application because Raidar checks your application's Read Level before doing anything that involves a Read and informs you that it cannot perform the requested activity and why.
Raidar has a potential problem with applications that write directly to the screen. It checks to see where you are writing to when you call it. If you are writing to the screen when Raidar is called, you will not have any problem if you also write to windows. The problem comes up when Raidar is called when you are writing to a window and then later close all you windows and write directly to the screen. The general rule that eliminates this problem is: "If you write to the screen, write to the
screen, if you write to windows, keep on writing to windows."
Raidar is sensitive to the platform that you are running on. In DOS Raidar will open in any one of the four modes that you set. It will either open as a minimized window, as a full window in the current video mode, or as a full window in 50 line mode (if supported on your computer) or as a menu pad on your menu. When running in Windows there are only two startup Modes: a minimized icon and a menu pad on your menu. When activated, the Raidar window takes up most of the screen.
5. Setting up Raidar for your computer.
Raidar keeps its defaults for both FoxPro for DOS and FoxPro for Windows in a .MEM memory files called RAIDAR.MEM. RAIDAR.MEM must be kept in the same directory as Raidar. When first called Raidar searches for this file and, if it does not find it, asks that you locate Raidar.APP specifically so that it can create the RAIDAR.MEM file in the correct place. If you find a file named RAIDAR.MEM in any directory other than the Raidar directory, delete it. It may cause erratic behavior.
Raidar keeps information about its default values in these files. The SETUP screen (different for DOS and Windows) is a task under the MODIFY menu pad. This sets up the default behavior of Raidar .
The primary choices of the setup menu include the following:
1. Show Title Screen. By default Raidar presents a title\copyright screen when it is loaded. You may suppress this only after you grow tired of seeing it and when we are not around. This will speed up access to RAIDAR.
2. Minimize Raidar on Startup. When Raidar installs in its own window you have to option of having the startup process minimize this window to either an icon (Windows) or a minimized window bar (DOS).
3. Set video display to maximum lines.
DOS behavior:
In DOS RAIDAR's default behavior is to install in full screen 25 line mode just below the system menu. If you have a VGA card, you can also cause RAIDAR to automatically switch to 50 line mode. If you choose this option, RAIDAR will switch back to 25 line mode when you exit RAIDAR (if you were in 25 line mode to start with.)
Hint: This is great for debugging. You can open the Debug and Trace windows in the lower half of the screen and watch your application run in the upper half.
WINDOWS behavior:
As there is no "expanded screen" modes in FoxPro for Windows Foxpro installs itself as a window in the screen and comes up minimized. Double click on the window and it will take over the screen.
4. Use Screen Mode always. Select this option only if you are running in DOS and only if your application does not use any windows. We are leaving this option in so that dBASE III+ applications running in FoxPro can use Raidar.
5. Turn off leftmouse key at startup. Raidar checks OKL settings to determine whether there is an On Key Label attached to the left mouse button. If there is the default behavior is to turn this On Key Label off. If Raidar turns off the left mouse button On Key label, it will turn it back on when you exit Raidar.
We strongly recommend that you allow Raidar to turn off any left mouse button On Key Label. Raidar uses the mouse as the primary navigation tool. If you leave the mouse button OKL active you might not be able to access the RAIDAR menu.
6. Display Raidar Warning messages. Raidar will give you plenty of warning if you are about to do something bad. If you enjoy life on the brink or simply don't care, you can suppress these warnings.
7. Power Developer's Library installed. (Commercial Plug) If you don't have Mac Rubel's Power Developer's Library, rush to the phone and order it now. Call 212-972-2330 RIGHT NOW! You will get the complete library and other goodies on disk. (End of commercial plug.) Once you have it, turn this option on. Include the library's directory in your FoxPro path statement. RAIDAR has organized the library by subject matter, with a description of each function and procedure. You may also display and edit the functions. Finally, you get access to Mac's Color Picker directly from the RAIDAR menu.
8. New library installed. Use this option to install a second (or third) library. You will be prompted for the path and name of the library and, if you have followed the skeleton of the FoxPro Power Developer's Library (see the manual for the Field Names and minimum file structure, you will have direct access to your library.
9. Install Raidar as a menu pad if possible. As discussed earlier, the behavior of Raidar changes greately based on your decision in this option.
When you install Raidar at a client site make sure that you do not bring the RAIDAR.MEM files with you. You should set up Raidar on each machine that you intend to use it each time you install the product at that site.
6. THE Raidar MENU
Raidar
for DOS and Raidar for Windows have similar menu structures. We will discuss the DOS menu and remark where it does not apply to the Windows product. We will also mention that areas were the Windows menu does not have a DOS counterpart.
A. The FILE Menu Pad
The first options of the file menu pad are all standard FoxPro FILE menu options. They are included in the Raidar menu only so that you have access to their function when editing files inside Raidar. In almost all circumstances they will not appear to be available to you. They are, however, necessary within Raidar nontheless.
Quit To options
The last three options deal with exiting Raidar . Unlike the FoxPro system menu, Raidar allows you to quit Raidar and go back to your running application, to the FoxPro Command window, or to DOS. The DOS quit is similar to the QUIT option in the FoxPro system menu.
Quit To Application
This option from the FILE menu pad will quit Raidar and put you back into your executing program "as if nothing had happened." This option is only available if you have entered Raidar while running a program of some sort. It is deactivated if you started Raidar from the command window. If you invoke Raidar on top of an .APP or .EXE file, the name of the application will appear in this option slot.
Care should be taken to exit Raidar at the same point in your application that you called it if you have lots of hot keys active in your program. Raidar resets ON KEY LABELS on exit and has to assume that it is exiting the program at the same point it entered. Exiting to your application at a point where there is a different set of On Key Labels active can be an interesting experience.
Quitting to your application removes Raidar from memory. All memory variables, windows, arrays, and menus associated with Raidar are released and control is returned to the running application.
Quit To FoxPro
This option exits Raidar and closes down everything that it can in your application before dropping you back to the command window.
This option has worked more than once to "gracefully" get out of an application that is "stuck" in an endless DO WHILE loop. It will close down your files properly before going back to the FoxPro command window.
Quitting to FoxPro closes down Raidar and all the files associated with the running application. You will find that this option will allow you to "gracefully" quit out of an application that is stuck and from which you cannot exit in any other fashion (other than the Big Red Switch or Ctrl-Alt-Del.) Using this option is far healthier. When you quit Raidar and return to your application Raidar purges its memory variables,
arrays, and menus from the system and leaves you with your running application.
Raidar is very direct in its approach to closing things down. This can sometimes lead to less graceful exits than others. If this is the case you may have to clean up after Raidar some. Do not assume that FoxPro is in a pristine state if you chose this option. One of the areas that Raidar cannot determine the status of FoxPro is with menus. There may be menus left on the stack (if you use this approach in your application.)
Note: This option is disabled if you are calling Raidar from a FoxPro .EXE program that is running outside of FoxPro. You can only quit to FoxPro if you are running your .EXE inside of FoxPro.
Quitting to DOS (or Windows for FoxPro Windows)
This option will not only quit your application, but will also quit the session of FoxPro as well and return you to either the DOS prompt or the next MS Windows window.
When Raidar is active in its own window it can sense what is happening in the running application better than it can when it is installed on an active menu. If, for example, you try to quit your application without quitting Raidar, in most cases Raidar will sense this and will automatically release the defined menu, popups, and memory variables. If it is installed on an active menu that also has a QUIT option, Raidar popups and memory variables may be left active if you QUIT without shutting down Raidar..
To compensate for this problem Raidar now installs a pseudo-system variable called _Raidar. When you call Raidar it declares this variable PUBLIC and sets it to TRUE. When you quit Raidar properly, the value is set to FALSE. If you wish you can include the following code in your QUIT option and Raidar will shut down properly with your application.
IF type('_Raidar') = 'L' .and. _Raidar && active Raidar!
DO Raidar WITH 'rd_quit' && run the cleanup code
ENDIF
With this code in your quit option Raidar will shut down with your application.
If you forget about quitting Raidar, or if you just want to reinstall Raidar on top of itself, the program will now allow you to do this. This is extremely helpful in those cases where some of the Raidar menu gets locked out by a modal read.
B. The EDIT Menu Pad
The Edit menu pad is a duplicate of the EDIT pad in FoxPro DOS. Raidar does not support some fancy FoxPro Windows options, but it does provide you with the full FoxPro editor capabilities while in the middle of your running application. This menu pad and all its options are here so that the full range of editing shortcut keys are available to you when you are editing snippets and files.
C. The ENVIRONMENT Menu Pad
The ENVIRONMENT Menu Pad deals with the status of the running FoxPro Application's environment in a very broad sense. By environment we must consider not only the Application's environment, but also the FoxPro Environment and the DOS environment that application runs in. The application environment is partially covered here. The FoxPro and DOS environment are covered totally in this section.
ON KEY LABELS - General
The first three options in the ENVIRONMENT popup have to do with ON KEY LABELS that are set in your application. It is important that you realize what happens behind these options when you invoke Raidar inside your running application. When you play with OKLs, you are playing with fire. Do not expect consistent results when you take off and put on hot keys while operating the debugger.
When you invoke Raidar one of the routines captures all ON KEY LABELS active at that instant. Raidar uses this list (array) of ACTIVE ON KEY LABELS for its entire debugging session. Raidar cannot know about new ON KEY LABELs that your application has either set or removed. It does not follow PUSH KEYs and POP KEYs. Actions that the application takes to modify the active ON KEY LABELS are not reflected in the listing. These overwrite expressed actions that you might think that you have taken by turning on or off ON KEY LABELs in the Raidar menu.
It is important that you RESET the ON KEY LABELs (option 3 from the ENVIRONMENT menu) at the same point in the program that you entered Raidar . The array of ON KEY LABELs are reset after the current settings are cleared out. If you reset the original ON KEY LABELS at some other point in the program, you might find that your application behaves differently than it should. This point also pertains to exiting Raidar . When you exit Raidar , the original ON KEY LABEL settings are put in force again. If you exit at a different point in the program with other ON KEY LABELS set, you will find that your program may not work as it should.
Toggle ON KEY LABELS on/off
Choosing this option activates a second popup. This popup contains six options. The first four of these allow you to toggle on or off ON KEY LABELs by category. The first category is 'Mouse Keys' and selecting this option will turn off all ON KEY LABELs associated with LEFTMOUSE, RIGHTMOUSE, and MOUSE. The second option in the sub-menu is 'Nav. Keys' and selecting this will turn off or on all ON KEY LABELs associated with cursor key movement. The third option is 'Function Keys'. As you would expect, selecting this option turns off all ON KEY LABELs associated with the function keys. The last group is 'Other Keys.' This group of keys includes the alphanumeric keys and miscellaneous keys not included in the three groups above.
The fifth option in the sub-menu is 'All Keys.' Selecting this option turns on or off all ON KEY LABELs globally. When keys or key groups are turned off a diamond appears next to the selection indicating that the key or group of keys has been deactivated.
The last option in the ON KEY LABEL sub-menu is 'Choose Key.' Selecting this option opens up another popup that contains a list of all ON KEY LABELs captured by Raidar when it was invoked. From this menu you can turn on and off ON KEY LABELs one by one. The only default Raidar behavior that can be modified when dealing with this menu is the status of the LEFTMOUSE button. We recommend a Raidar default (set from the Raidar setup menu found in the MODIFY menu option) that will turn the ON KEY LABEL associated with the LEFTMOUSE button OFF at startup. We have found that this will allow you to use Raidar in all circumstances. Not selecting this option can cause conflict between Raidar and you application if you have a particularly invasive ON KEY LABEL attached to the LEFTMOUSE button.
View OKL Status
The second popup option for the ENVIRONMENT popup is "View OKL Status." This option allows you to look at all ON KEY LABELs in the array, their current status, and the actions assigned to them. Should you need to find out exactly what is going on at that instant in time then you can use the 'Run FoxPro Command' option available to you on the Debugging menu. Run DISPLAY STATUS and you will get an unexpurgated copy of the current FoxPro status, including current ON KEY LABELs.
Reset Original OKLs
As discussed above, the third option in this menu resets the original ON KEY LABEL settings you your application. Take care to do this only when you are at the same point in the application as you were when you invoked Raidar . The debugger will post a warning message to this effect also before allowing you to proceed.
The next section of the ENVIRONMENT popup deals with the FoxPro environment in which your application in running. This section provides several services for you. Unlike ON KEY LABELs, the options in this section are dynamic. The contents reflect FoxPro's state at the moment you select this option. The contents change as you move through your application.
Procedure Stack
The first option of this sub-group is the 'Procedure Stack' option. It shows you the complete calling stack of your running application at the time that you call this option. The master program is at the top of the stack and the currently executing program is at the bottom. This option can be valuable to you in situations where there are more than one way to get to a specific code segment.
Note: Another way to get at the calling stack is to look at the bottom of the Program option in the TRACE window display. It is often hidden below the window. Click on the bottom of the frame and it should move the calling stack into view for you.
Memory Display
This option shows the names and contents of all application memory variables, menus, popups, and windows defined at that moment.
The system resources that Raidar is using are purged from the display when Raidar creates the display file. As the display is actually a text file you can scroll this display forwards and backwards and use the FoxPro search capabilities to locate a specific item.
The memory numbers shown in this display are approximate numbers only. We know what the base memory usage of Raidar is and subtract that amount from the total reported by FoxPro. If you have invoked Raidar in a particularly complex situation, the memory used by Raidar will be higher. The extra usage will be reflected in the amount of memory used by your application.
Note: In FoxPro for Windows the font used for this option is inherited from the FoxPro system window. If you do not like the display, experiment with the system window font. (FoxFont 7 gives you a readable monospaced output.)
Display Memory Like
This option of the Environment menu pad prompts you for a file skeleton. Leaving the option blank will cause the process to terminate. Enter an asterisk (*) and you will receive a complete display of all memory. Enter a letter or letter combination and the option will return a display of only the memory variables that meet the skeleton criteria.
Note: In FoxPro for Windows the font used for this option is inherited from the FoxPro system window. If you do not like the display, experiment with the system window font. (FoxFont 7 gives you a readable monospaced output.)
Status Display
This option allows you to look at the entire FoxPro "Display Status" listing. Unlike the normal DISPLAY STATUS command, when you call for this option in Raidar you will be looking at a text file. You can scroll forward and backward through the file and use FoxPro's Find capability as well. The status display is a complete, unexpurgated listing of the FoxPro's Display Status listing.
Note: In FoxPro for Windows the font used for this option is inherited from the FoxPro system window. If you do not like the display, experiment with the system window font. (FoxFont 7 gives you a readable monospaced output.)
Get All (Panic)
Calling this option of the Environment menu stores the Status file, Memory file, certain environmental variables, the calling stack and the status of all open data tables to a file named PANIC.TXT. It also stores the names and values of all memory variables to a .MEM file called PANIC.MEM and stores this file in the current FoxPro default drive.
PANICxxx files increment each time you call the function. They start at PANIC001.TXT/MEM and increment to PANIC999.TXT/MEM. Delete the files when you no longer need them or they will take over the world.
You have the option of viewing this file interactively before returning to your application.
Note: In FoxPro for Windows the font used for this option is inherited from the FoxPro system window. If you do not like the display, experiment with the system window font. (FoxFont 7 gives you a readable monospaced output.)
About FoxPro
The final option in this section of the Raidar Environment Menu Pad is the 'About FoxPro' option from the main system menu.
Index to Mac Rubel's Power Developer's Library
The next section of the ENVIRONMENT menu is the libraries management section. Raidar is fully compatible with FoxPro 2.0 Power Tools and Mac Rubel's FoxPro 2.5 Power Developer's Library. This library can be installed from the Raidar setup menu.
This option of the Environment menu won't mean much to you unless you have a copy of Mac Rubel's FoxPro Power Developer's Library. If you have a copy of the library installed in a directory included in your FoxPro path statement, you may use this selection to find the right procedure or function for the job at hand. You may also view and modify the procedure or function. Be sure you have checked the Power Developers Library box on the Raidar Setup screen. See the Raidar Help topic on this subject for further details.
In version 2.4 we included an index to Mac Rubel's FoxPro 2.0 Power Tools. The FoxPro Power Tools book was not updated for FoxPro 2.5. Instead Mac wrote a library of over 450 cross-platform functions for FoxPro DOS and FoxPro for Windows. As part of the library's installation process, it searches for a copy of the Raidar browser file and, if it finds it, overwrites it with a new copy. If it does not find the file it simply creates a new Raidar browser .dbf. The file's name is FPPD.DBF.
New Library
Beyond this default library you can add any number of libraries yourself. Libraries are stored in FoxPro data tables. Each library table must have as a minimum, the following structure:
| Field Name | Field Type | Field Length |
| PRG | Character | 8 |
| SUFFIX | Character | 3 |
| CATEGORY | Character | 20 |
| DESCRIPT | Character | 60 |
The file must contain the following indexes created in the listed order:
| Index Tag | Expression |
| CATEGORY | CATEGORY Unique |
| ALL | CATEGORY + PRG |
| PRG | PRG |
You may have any number of additional fields in this table. You may also have as many additional tags as needed. These minimums, however, must be maintained if the library manager is to work properly.
To create a new library go to the setup screen (see previous section) and choose the selection for adding a new library. Raidar will ask you a series of questions about your new library or, in the case of an existing library which you are activating, verify that the library structure is properly constructed. The name of your library will be added to the Raidar menu.
If you have followed the above guideline, you will find that you will be able to add new elements to your library on line, access them, and use them within Raidar without any problem.
View Config.fp, Config.sys, and Autoexec.bat
The next to last section of the ENVIRONMENT menu pad allows you to view the contents of the three configuration files that affect the way that your application might work. The first of these is the FoxPro configuration file. Raidar will look for and then look at either the Config.fp file (FPD) or the Config.fpw (Windows) file, depending on which product is currently running. It allows you to view the contents, but not modify them.
The next two options on the ENVIRONMENT popup allow you to look at the Config.sys and Autoexec.bat files that DOS uses when you boot your computer. Again, these files are in the view mode only. No modifications are allowed.
View SET
The lasts option in this menu popup is the View SET option. This allows you to look at the current DOS environmental variables and their values. You cannot change the value of these variables from within Raidar . You must first exit back to the DOS prompt to add or change environmental variables.
The View Environment Settings option RUNs a DOS command. If you are running FoxPro for Windows and a DOS window is left on your screen after running this option you can first close the window down (no harm done) and then modify the FOXPROW.PIF file to instruct Windows to CLOSE WINDOW ON EXIT.
D. The DEBUGGING Menu Pad
Debugging is what you would expect a debugger to do and Raidar is no exception. This popup menu permits access to most of the debugging tools available to FoxPro and some that are not.
Debug
This Raidar Debugging option has a menu shortcut key attached to it (^D). Choose this option either with this key or by selecting from the menu. If the Debug window is not open or visible, it will be activated. If the debug window is open and visible, choosing this option will deactivate (but not release) the DEBUG window.
Hint: You can toggle the debug window and its contents on and off using the ^D menu shortcut key. Load the debug window up with the information that you need and then hide it using ^D. When you reach the point where you need to look at values press ^D again to see the window.
Note: This option is disabled when running a FoxPro application that has been packaged as an .EXE file when that .EXE file is running outside of FoxPro (in a stand-alone mode.)
Trace
This option has a menu shortcut key attached to it (^T). Choose this option either with this key or by selecting from the menu. If the Trace window is not open or visible, it will be activated. If it is open and visible, choosing this option will deactivate (but not release) it.
Hint: The Trace window contains a lot of good information that is not normally known. You can set breakpoints in programs while they are running, modify execution speed, and even CANCEL a running application from the popup that is contained inside the Program option of the Trace menu. (If you scroll down the menu list you will even be able to see the calling stack for the current application.)
Note: This option is disabled when running a FoxPro application that has been packaged as an .EXE file when that .EXE file is running outside of FoxPro (in a stand-alone mode.)
Set Step
Choosing this option will SET STEP ON . Choosing this option will activate the TRACE window if it is not already activated, will make the Trace window the active window, and will put your program into the step-at-a-time trace mode. To resume normal trace operations choose Resume from the menu in the Trace window or type RESUME in the Command Window.
SET STEP ON is invaluable for stepping through your application code. Unfortunately TRACE does not know if it is your code or Raidar's. As no source code is available for Raidar, care should be taken not to call Raidar routines with SET STEP ON. It is not fatal, just annoying.
Note: This option is disabled when running a FoxPro application that has been packaged as an .EXE file when that .EXE file is running outside of FoxPro (in a stand-alone mode.)
Throttle
Choosing this option allows you to set the execution throttle for FoxPro. You can slow down execution to follow program logic by setting a non-zero value in this option window.
In FoxPro for Windows this option is controlled by a spinner.
Selecting Clear as your exit option will reset the throttle to 0 for fast operation. Selecting Cancel will retain the throttle value prior to selecting the option.
Note: This option is disabled when running a FoxPro application that has been packaged as an .EXE file when that .EXE file is running outside of FoxPro (in a stand-alone mode.)
Set View
The Set View option of the debugging menu pad give you direct access to the FoxPro VIEW Dialog. Be careful if you decide to change values here because the values are global and may affect your application.
Note: This option is disabled when running a FoxPro application that has been packaged as an .EXE file when that .EXE file is running outside of FoxPro (in a stand-alone mode.)
Change Display Size
The Change Display Size option of the Debugging menu is available only when Raidar is running in FoxPro for DOS. The menu option has its own menu shortcut key combination of ^S.
If you are running FoxPro for DOS and you have a display that offers 43 or 50 line mode, this option will toggle you back and forth between 25 line and extend video modes. (Good for debugging!). If you are running FoxPro inside of DesqView, good luck! You might want to stay away from this. DesqView gets nervous and jerky when you mess with display size.
Calculator, Calendar, ASCII and Special Characters
The next two (FoxPro for Windows) or four (FoxPro for DOS) options in the Debugging menu are calls to the FoxPro Calculator, Calendar, Extended ASCII chart, and a list of the special extended ASCII characters. Using the calculator and the calendar will change the values in the FoxPro system memory variables _CALCVALUE and _DIARYDATE.
Run FoxPro Command
The next option in the Debugging menu is perhaps one of the most powerful but also one of the most dangerous. 'Run FoxPro Command' gives you direct access to all FoxPro commands and functions. You can enter commands in the entry window and view results in the output window.
Having access to the FoxPro command window is a loaded gun. It is very possible to enter a command that will cause your running application to malfunction. (CLOSE ALL comes to mind.) If this happens, Raidar will remain active. Using the 'FoxPro' option from the FILE menu, you can gracefully return to the command window without further messing up your application.
Being able to enter FoxPro commands has several advantages. From this window you can change the record pointer on open files, look at the values of variables, even open a new file in an unused work area. The possibilities are endless. It is, however, up to you to remember where you are in your running application and what affect the commands that you issue will have on it.
Hint: Although this option is a loaded gun (see warning above) this option allows you ultimate flexibility while within Raidar. You can even close down Raidar from this option by using the command "DO Raidar WITH 'rd_quit'"
Run EXT_RAID
Choosing this option from the Debugging menu allows you to run your own debugging routine from within Raidar. The routine must be named EXT_RAID.PRG and it must be visible in the FoxPro path.
Raidar PUSHes On Key Labels onto the stack before calling the program and POPs them off after we are done, but we do not guarantee anything in between. You are on your own on this one!
Shell to DOS
This option allows you to shell out of FoxPro to DOS. Raidar and your running application keep about 140,000 bytes of space in your system, giving you access to the rest of memory to run your DOS services. Typing EXIT returns you to the point where you left your application.
Hint: If you have to change directories when you run this command, make sure that you change the directory back to the one that was in use when you called this function. Failure to do this changes the FoxPro default directory and may have unintended consequences on the performance of you application.
FoxPro Help
Raidar
gives you access to FoxPro Help. Selecting this option allows you to look up any topic included in the FoxHelp table. Raidar warns you that it is going to SET HELP TO FoxHelp and that it will turn help on and ask if you really want to do this. If you answer Yes, FoxHelp will be activated and you can enter a help topic in the input window. Help for that topic will be displayed. If you have another help file open as the FoxPro Help file it will be your responsibility to reset that help file after you finish with FoxPro help. You can do this with the 'Run FoxPro Command' option from this menu.Note: This option is disabled if you are calling Raidar from a FoxPro .EXE program that is running outside of FoxPro.
E. The TABLES Menu Pad.
The Tables option from the main Raidar menu opens up a dialog box containing a scrollable list of all the tables that were open when the option was called. After selecting the table of your choice you have the option of viewing the structure of that table, the contents of the current record of that table, all the indexes that are currently open for that table, the relations set between that table an all other open tables, and the filter condition set on that table.
When you view the indexes open on any table the option will list all open .IDX files first, the tags in the production .CDX second, and tags in any secondary .CDX files last. The tag numbers and names are given along with the index expression for each index. The controlling index (if the table is set in an index order) will be indicated by two asterisks after the tag number.
Relations set between the marked file and any other open data tables are noted when you call this option. If there are no relations set for the highlighted file, Raidar tells you this.
Raidar will show a filter set on the highlighted file in the output window if one is set. If there is no filter condition, Raidar will tell you.
F. The MODIFY Menu Pad
The 'Modify' menu allows you to edit all of your application files, memory variables, colors, and set up Raidar to act as you wish. The Modify Menu pad is the heart of Raidar's development side.
Modify Current Project
If your application is packaged as an .APP or an .EXE file we assume that there is a .PJX file associated with it. If this project file is in a directory that is included in the FoxPro path then Raidar can see it and will load it.
The MODIFY Current Project option opens a selector dialog box containing a list of all the files in your application. You have the option of filtering them by type by pressing any one of the radio buttons listed below the scrollable list. Doing this restricts the list to only those files that meet the criteria. The criteria are as follows:
ALL - displays all files included in the project.
PROGRAM - displays only .PRG files
SCREEN - displays only .SCX files
REPORT - displays only .FRX files
LABEL - displays only .LBX files
QUERY - displays only .QPX files
MENU - displays only .MNX files
BMPs - displays only .BMP files
If you select a program file (.PRG, .SPR, or .QPR file), Raidar will open that file for you using MODIFY COMMAND. You will be able to edit the file just as you would if you issued the command from the command window.
If you select a Screen, Report, Label, Query, or Menu file source file (.SCX, .FRX, .LBX, .QPX, or .MNX files), Raidar will open the appropriate design tool for that file type and will allow you to edit, modify, add, or delete information from the design surface and the associated snippets.
Raidar opens up graphic files for view only and does not open up .FRM or .LBL files. Raidar will not open up compiled code files (.FPX, .SPX, .MNX, or .QPX), Applications (.APP), executables (.EXE), or library files (.PLB, .DLL, or .FLL).
Raidar will try to open any other file type using the MODIFY FILE command.
Note: Depending on whether a FoxPro System Menu of any sort is present when the modify request is made, the special menu pad that is associated with each of the design surfaces may or may not be visible. If it is not visible the shortcut keys that are associated with the design surface will work but you will not be able to access the menu pad.
Note: When running an .EXE file outside of FoxPro (using the runtime support libraries) Raidar will not allow you to edit screen, menu, query, label, or report files. These actions are not supported.
Note: When running Raidar in FoxPro for Windows the text displayed in the window when modifying program code or text files assumes the font characteristics of the basic FoxPro screen. If you do not like the way that the display looks, you must change the underlying font specification for the FoxPro window before starting your application.
Select Project
The Select Project option of the Modify menu operates in exactly the same fashion as the Modify Current Application option does. The only major difference is that you have the option of selecting any other project that you want to load. The browser and design surgaces work on the selected application's .PJX file.
Modify Files
The Other Files option of the MODIFY menu pad allows the user to edit any file that is accessible to FoxPro using the GETFILE() Dialog. All files and file types are allowed.
If you select a program file (.PRG, .SPR, .MNR, or .QPR file), Raidar will open that file for you using MODIFY COMMAND. You will be able to edit the file just as you would if you issued the command from the command window.
If you select a Screen, Report, Label, Query, or Menu file source file (.SCX, .FRX, .LBX, .QPX, or .MNX files), Raidar will open the appropriate design tool for that file type and will allow you to edit, modify, add, or delete information from the surface and the associated snippets.
Raidar opens up graphic files for view only and does not open up .FRM or .LBL files. Raidar will not open up compiled code files (.FPX, .SPX, .MNX, or .QPX), Applications (.APP), executables (.EXE), or library files (.PLB, .DLL, or .FLL).
Raidar will try to open any other file type using the MODIFY FILE command.
Note: Depending on whether a FoxPro System Menu of any sort is present when the modify request is made, the special menu pad that is associated with each of the design surfaces may or may not be visible. If it is not visible the shortcut keys that are associated with the design surface will work but you will not be able to access the menu pad.
Note: When running an .EXE file outside of FoxPro (using the runtime support libraries) Raidar will not allow you to edit screen, menu, query, label, or report files. These actions are not supported.
Note: When running Raidar in FoxPro for Windows the text displayed in the window when modifying program code or text files assumes the font characteristics of the basic FoxPro screen. If you do not like the way that the display looks, you must change the underlying font specification for the FoxPro window before starting your application.
Memory Variable
Choosing this option from the MODIFY menu pad allows you to change the value (but not the type) of any memory variable. First you must identify the name of the memory variable. If it exists you are given the current value and asked for a new value. The new value takes effect immediately.
Note: There is a problem with trailing blanks if your memory variable is of the character data type. A TRIM() has been put in (version 2.53) that cuts off all trailing blanks. If you need to have your trailing blanks use RUN FOXPRO COMMAND to change the value of the variable.
Color Picker
Raidar
for FoxPro DOS and Raidar for FoxPro Windows diverge in this area. In FoxPro DOS you have access to the Power Tools Color picker. In windows you have access to the Windows Color Dialog. Changing colors in DOS affects the current session only. Changing colors in Windows affects the MS Windows defaults for all applications. Depending on how you have Windows set up, the color change can be permanent.
Windows Desktop
Raidar
for Windows allows you access to the Windows Desktop Setup Dialog. As with the Windows Color selector, the changes you make here may persist beyond the boundaries of your application and the Windows session.
Extended Character Set
The extended ASCII option accesses the extended windows characters for the current font. Accessing this allows you to insert special characters in your files.
Setup Raidar
The last option in the MODIFY menu is the Raidar setup option. This has been covered in detail in the section on setting up Raidar and will not be duplicated here.
G. The WINDOWS Menu pad
This option allows you access to all of the capabilities of the WINDOWS menu pad on the main system menu. We have found circumstances where you are "locked out" of this option by an event loop that restricts access to these services. If this happens it is because of the way you are coding. There may be nothing wrong with your code, but the loop prevents you from seeing the contents of this window.
H. The Raidar Help Menu Pad
Included in the
Raidar Help menu option are condensed help topics on the Raidar
debugger. Choose the area that you are interested in and find out more about how to use
Raidar . This help system is driven by a small data table that is included in RAIDAR.APP. Help customization is not possible.
The Raidar version number is included in the Help file. Please consult this when filling out your registration.
7. WHAT TO DO IF SOMETHING GOES WRONG.
We spent an incredible amount of time that went into trying to "bombproof" Raidar . We are justifiably proud of our product but are also aware that there will be situations where Raidar will fail. There is no way that we can anticipate and test all possible application environments. For this reason we have built "Raidar Soft Landing" into Raidar .
There are several places where Raidar can and will intercept errors as they are happening. "Raidar Soft Landing" (don't you just love it!) will notify you of the problem and will either attempt to correct the problem itself or put up a message telling you that something that it cannot handle has happened. In the worst case it will allow you to suspend your application and go back to the FoxPro Command Window to figure out what has happened. Our experience suggests that it is best not to suspend the application unless it is absolutely necessary.
There will be some cases where this "Raidar Soft Landing" will not work. Should you experience such a situation while running Raidar please do the following:
1. Try to capture the current situation to PANIC.TXT using the GET ALL option from the Environment menu. This will tell us where you were when things went bad.
2. Try to close Raidar back to the FoxPro command window. In the process Raidar will close down your application in as graceful a manner as possible. All files will be properly closed and you will not lose any information.
3. Restart your application after releasing all memory and attempt the same activity again. If it happens, collect all the information that you have on the problem before talking to us.
4. Talk to us. We are available. We are interested in your problems. The telephone numbers for Performance Dynamics are:
1-212-972-2330 (voice)
1-212-972-2332 (fax)
Our CompuServe numbers are located in the ABOUT choice in the INFO menu option. We are supporting Raidar in the third party section of the FoxForum and prefer to answer questions about the product there. Make sure that Raidar appears in the message header.
The idea behind Raidar is that it will work properly and without conflict in all situations. We have spend a considerable amount of time trying to make this a reality and in most cases we have succeeded. There are, however, places were this is just not so. This Raidar Help topic deals with some of the known situations and what you can do about them.
I. I have installed Raidar and all of a sudden it is no longer on my menu. I press Ctrl+PgUp to get to the menu and FoxPro gives me an error message that says " POPUP NOT DEFINED."
Most probably you have PUSHed the menu that Raidar attached itself to and are operating with a different menu. When you PUSH the menu the popup associated with the pad (the Raidar menu) is pushed also. To get around this problem you should go back to the original program state where you installed Raidar and release it from you menu. You should then go to the new program state that you want to call Raidar from and reinstall it on the menu that is active at that time. You can install Raidar on any number of menus but its behavior becomes erratic. We do not recommend this.
2. I cannot see the Raidar Window and cannot get at it!
If you have installed Raidar as a minimizable window it is quite possible that your own windows will place themselves on top of the minimized window. The window is still there, but you cannot see it. Use the Ctrl+PgUp key combination to bring the Raidar window to the top and to maximize it. When you have finished with Raidar you can use the Ctrl+PgDn key combination to minimize Raidar once again.
3. Things are showing up inside the Raidar Window!
The Raidar window is just a window like any other FoxPro window. If this happens it is because your application code is activating windows in an area already occupied by the Raidar Window. While there is no problem with this, it does not look right. If you are running in Windows the solution to this is to keep Raidar minimized until you need it and to minimize it again as soon as you are finished with it. If you are running Raidar in DOS, the best solution is to go to 50 line mode (Ctrl+S will get you there) and to run Raidar in the lower half of the screen and your application in the top half. The best solution of all is to try installing Raidar on your menu. Do this by changing the Raidar setup in Raidar 's MODIFY menu. If you do this, you will not have to worry about conflicting windows.
4. I have installed Raidar on my menu and am now in an Edit screen where the menu is hidden. I need to get to Raidar but cannot get to the menu.
Use Ctrl+PgUp. It will pop up the Raidar popup for you. It may also pop up stuff that you don't want as well. Don't worry. When you leave the edit screen everything will return to normal. If it does not, use your hot key and reinstall Raidar .
5. I have opened a screen from my application using the MODIFY Current Application option. When I open the screen it tells me that there are objects that are different from platform to platform. What should I do?
Open the project as is or Cancel. The transporter will not find a needed memory variable and will cause an error. Transport all screens outside of Raidar if you can.1
6. I am getting an "Out of Memory" error when I try to install Raidar or when I run a Raidar task.
The plain truth is that Raidar does take some memory. First of all the window and the Raidar Menu take up memory. Second, any time you open a task it is going to take memory whether or not it is inside your application or inside Raidar . If you are getting this message you are running pretty close to the edge. If you are in DOS you can experiment with your memory manager and try to squeeze another couple of k of memory out of your system. If you are running FoxPro for DOS inside Windows, look at your PIF file to make sure that you provide the maximum amount of memory for FoxPro that you can. (Use 640 as your value.)
7. I am in a READ and I want to access the Raidar menu. I click on it and all the options are deselected.
Your READ is modal. You cannot access Raidar (or other menu commands) when you are in a MODAL read.
Typical Raidar Problems and Suggestions
We have included a list of several normal Raidar situations and suggestions on how to deal with them. Please check the Raidar Help section of the program for the latest information..
1. I cannot see the Raidar Window and cannot get at it!
If you have installed Raidar as a minimizable window it is quite possible that your own windows will place themselves on top of the minimized window. The window is still there, but you cannot see it. Use the Ctrl+PgUp key combination to bring the Raidar window to the top and to maximize it. When you have finished with Raidar you can use the Ctrl+PgDn key combination to minimize Raidar once again.
2. Things are showing up inside the Raidar Window!
The Raidar window is just a window like any other FoxPro window. If this happens it is because your application code is activating windows in an area already occupied by the Raidar Window. While there is no problem with this, it does not look right. If you are running in Windows the solution to this is to keep Raidar minimized until you need it and to minimize it again as soon as you are finished with it. If you are running Raidar in DOS, the best solution is to go to 50 line mode (Ctrl+S will get you there) and to run Raidar in the lower half of the screen and your application in the top half. The best solution of all is to try installing Raidar on your menu. Do this by changing the Raidar setup in Raidar 's MODIFY menu. If you do this, you will not have to worry about conflicting windows.
3. I have installed Raidar on my menu and am now in an Edit screen where the menu is hidden. I need to get to Raidar but cannot get to the menu.
Use Ctrl+PgUp. It will pop up the Raidar popup for you. It may also pop up stuff that you don't want as well. Don't worry. When you leave the edit screen everything will return to normal. If it does not, use your hot key and reinstall Raidar .
4. I have opened a screen from my application using the MODIFY Current Application option. When I open the screen it tells me that there are objects that are different from platform to platform. What should I do?
Open the project as is or Cancel. The transporter will not find a needed memory variable and will cause an error. Transport all screens outside of Raidar if you can.
5. I am getting an "Out of Memory" error when I try to install Raidar or when I run a Raidar task.
The plain truth is that Raidar does take some memory. First of all the window and the Raidar Menu take up memory. Second, any time you open a task it is going to take memory whether or not it is inside your application or inside Raidar . If you are getting this message you are running pretty close to the edge. If you are in DOS you can experiment with your memory manager and try to squeeze another couple of k of memory out of your system. If you are running FoxPro for DOS inside Windows, look at your PIF file to make sure that you provide the maximum amount of memory for FoxPro that you can. (Use -1 as your value.)
6. I have sucessfully installed Raidar and now, all of a sudden, when I call it i get a FoxPro error message stating that it cannot find Raidar .
When Raidar starts it creates its menu then it "goes away." After Raidar installs itself it is no longer in the calling stack. The menu is all that remains active. Each of the menu choices calls Raidar with a "DO RAIDAR WITH parameters" call when the user selects an option. This is how Raidar manages to stay out of the way while you run you application. If you change your path RAIDAR .APP may not be visible on the FoxPro Path. The fact that you have successfully installed Raidar does not preclude the possibility that the PATH statement may change at a later point in the application. Raidar must be visible to FoxPro for the product to work.
We are committed to making changes to Raidar to handle as many environments as possible. Please let us know your problems and suggestions. Any input that results in an improvement to Raidar will qualify you for a free upgrade to that version of the product.
Thank you again for buying and using our product. We hope you find it as useful as we do.
Frank Donovan
Mac Rubel
Raidar License
Raidar
is licensed to you as a single developer. This copy of the program is licensed to you and you alone. You have the right to have copies of Raidar on more than one development machine. You also have the right to temporarily install Raidar on client machines for your own use. You may maintain as many working copies of Raidar that you need so long as only you use these copies of RAIDAR .APP.As a developer you also have the right to place RAIDAR .APP on any client machine where real-time debugging might be necessary. You have the right to use Raidar to provide you with information about what is going on with your programs at such client sites. It is your responsibility to code your applications in a manner that restricts access to Raidar to yourself only. This copy of Raidar is not licensed to any third party.
Multi-use licenses and site licenses are available from Performance Dynamics Associates. Please contact us for details.
Please fill out the registration form found at the end of this manual and return it to:
Performance Dynamics Associates
Raidar Registration
305 Madison Ave. Suite 1420
New York, NY 10165
FoxPro, Microsoft, MS Windows are all registered trademarks of Microsoft Corp.
Raidar is copyright 1993
Performance Dynamics Associates
All Rights Reserved
Raidar REGISTRATION
First Name: ________________________
Last Name: ________________________
Company: ________________________
Address 1: ________________________
Address 2: ________________________
City: ________________________
State: _____ Zip: __________
Country: ________________________
Telephone: ________________________
CIS #: ________________________
Raidar Version Number: ____________