If you chose to install QuickCup using the program group that was suggested, then the program group will be called, appropriately, QuickCup. Otherwise, in these instructions, substitute the alternative name you chose...

To start the QuickCup application, click on the button on the Windows desktop, and click on the Programs menu that pops up. Then click on the Quickcup menu that appears to the right, and finally, click on the menu item to launch the application.

Creating a desktop shortcut

If you wish to create a desktop shortcut for the application, right-click over the button on the Windows desktop, and select the Open menu option. Double click on the icon marked Programs and then double-click on the icon (program group) marked QuickCup.

Now right-click over the icon. Click on the Send To menu, and then click on the Desktop (create shortcut) menu option.

A shortcut icon has now been created on your desktop. You may now double-click on this icon in the future to obtain access to the program, if you prefer.

To clean-up, close the QuickCup window, and then the Programs window, and then the Start Menu window by clicking in the at the top-right hand corner of each of these windows.

Parts of the program

It is useful when reading through the documentation to understand what the different parts of the QuickCup application are, what they are called, and also their purpose.

The Title Bar

The top part of the screen is the title bar, which shows the name and version of the application as follows:-

The icon at the top-left hand corner is the icon when you first start the application, and helps to identify the program. It is also the icon which appears in the task bar at the bottom of the Windows desktop to show you which applications you have open on your computer.

You can see that the title bar shows the name of the application, the version number, and a copyright notice. The three buttons at the right-hand side of the title bar perform the following respective functions:-

Minimize the QuickCup application, so that it disappears from the desktop, but remains available on the Windows task-bar at the bottom of the screen. View it again by clicking on the QuickCup button on the task bar.
Maximize the QuickCup application. This makes the application window fill the entire size of the screen, if you wish to see the maximum amount on the screen at one time. Clicking the middle button again restores the window to its previous size.
Close the windows. Effectively, this closes the QuickCup application.

The Menu

The menu is the line of text just below the title bar, and looks like this:-

It is used to select different functions from within the QuickCup application. Each of the words on the line (known as the menu bar) represents a type of function that can be performed.

To access one of these words, either click on the word with the mouse pointer, or hold down the Alt key and press the first letter of the word that you wish to use (e.g. to access the Compile menu, hold down the Alt key and press the C key). You may notice that the key you press is the key that appears as underlined in the word.

The menus' functions are as follows:-

File menu - Creating and Opening new projects and source code files.
Edit menu - Various functions for helping to amend source code
Compile menu - Used to check whether your source code is structurally correct, and create bytecode files
Run menu - Used to test that your source code operates correctly
Archive menu - Used to package your source code into a single compressed file known as a JAR file
Help menu gives access to various information about the application, such as this help, access to the web site, and copyright details.

When you have chosen a topic area, a list of options will drop down from the menu word that you chose, and from these you can choose the function that you wish to perform. These are detailed in the Quick Function Reference section.

The Toolbar

The toolbar appears just below the menu, and consists of a number of buttons with pictures (or icons) on. If you hover your cursor over each of the buttons, a small box will appear above the button (known as a ToolTip) to give a brief explanation of the button's function.

When you are clicked on the Settings tab, the toolbar will look like this:-

When you are clicked on any other tab, then a few more of the buttons become available (find, replace, and goto) as they are related to text-editing:-

Notice that the Save button is greyed unless a change has been made either to the project details or one of the files attached to the project. This indicates whether something in the project needs to be saved.

Each of the buttons (except for the last, Show Console Window button) have a direct equivalent in the menu. They are as follows:

Save: Save any changes to the Project / Attached files.
Print: Print details of the currently selected tab (either project or source code details).
Find: Find text in the currently selected attached file.
Replace: Find and Replace text in the currently selected attached file.
Goto: Go to (or check) a line number in the currently selected attached file.
Compile: Compile the main project class file.
HTML Page: Preview the applet on its web page using the default web browser.
Launch Applet Viewer: Preview the applet using the AppletViewer application.
Launch Application: Launch a Java application.
Archive to JAR file: Archive non-source Project Directory files to a JAR file.
Show Console Window: bring the console window to the top.

The tabbed notebook

The application is split into different 'tabbed pages' in a notebook style. The tabs look like this:-

When you click on one of the tabs, you will see information relating to the title of the tab. The first tab relates to project settings, and any other tabs relate to files that are attached to the project, and available for editing. You can see in this example, that the selected tab looks like it is at the front of the others (TextBurst.htm) and that the text of this file has been altered (the title has an asterisk '*' after it).

The settings tab

The settings tab gives the main 'global' information relating to the currently active project. Most of the information in this section is saved with the project (.qjp) file.

The settings tab is divided into different sections, each enclosed by a box:-

The 'Project Properties' section

This section relates to identifying information about the project.

Autoload last opened / saved file when next launch QuickCup?
This option is not stored with the project - it indicates whether the project currently selected should be re-opened automatically when you next start-up QuickCup. If you wish to start from a blank project, and manually select which project to open each time you use QuickCup, then uncheck this option (i.e. take the tick out of the box).
Project Filename
This shows the drive, directory/folder, and filename where the project is stored. Note that if you change this, then all of the details of the project will be retained, but the next time you save, the project file will be stored in a different location. Copies of the attached files are not taken - you are still linked to the same file, but now from a different project.
In this way, you can create new projects with similar details - you may wish to unattach files and attach new files.
If you wish to open a new project, you can click on the button to the right of the text box, and an Open File dialog box will be displayed. Click here for other methods of opening a project file.
Title
Enter into this box a name for the project - this should be a brief description.
Description
Enter into this box further information about the project. This may be more details on the purpose of the program, a history of changes, notes on changes that need to be made, or more detailed instructions on how to operate the application.

The 'Files in Project' section

This section relates to the files attached to the project. These are generally files that you would want to edit using the inbuilt text-editing facilities of QuickCup. However, if you wish to compress files into a JAR file that only appear in the project (for example, if you have multiple projects in one directory), you can also add ineditable files - just be careful not to inadvertently edit them!

Typical files you would wish to add to a project might be Java Source Code files (end with .java), HTML Source Code files (end with .htm or .html), and possibly text data files (usually end with .txt).

To add a file, you can either type the name into the text box at the bottom of this section directly (in which case, the text will appear in red until you have typed a valid filename, at which time it turns to black), or you can click on the button to use a dialog box to select which directory and file you wish to add to the project, which will fill in the text box for you.

Once you have the correct filename in the edit box, click on the button to add the filename to the list of files attached to the project. If the file is a standard editable file, a tick will be placed next to it, and a new tab created from which you can edit the file.

If you wish to close this tab without removing the file from the project, click on the tick next to the file. Click on the empty box to place a tick back again to re-open the file, and create a tab to edit the text again.

If the file you add is the first html file added to the project, it will automatically be assigned to the Main HTML File heading. This is the filename of the web page which will be used if you choose to launch the applet using either your default web browser or the applet viewer.

If you wish to change which html file is used to perform these functions, click the filename in the list of attached files to highlight it (not the tickbox), and then click on the button that displays the current Main HTML File. Note that the filename must end with either .htm or .html

If the file you add is the first java source file added to the project, it will automatically be assigned to the Main Java File heading. This is the filename that is compiler if you click on the button to compile the project, and also the filename used to launch an application.

If you wish to change which java source file is used to perform these functions, click the filename in the list of attached files to highlight it (not the tickbox), and then click on the button that displays the current Main Java File. Note that the filename must end with .java

If you wish to remove a file from the project, so that it is no longer available for editing within the QuickCup environment, click on the filename you wish to remove in the list (not the tickbox), and click on the button to the left of the edit box.

Note that if you increase the size of the window, the visible space for the list of files attached to the project will be increased accordingly.

The 'Java Developers Kit (JDK) Environment Information' section

This section relates to how to access the standard Sun™ tools, such as the compiler, application launcher, applet viewer, and other miscellaneous tools. In order to use these tools, QuickCup needs to know where they are stored.

When you install the Java Software Development Kit (JDK) from their web site, you will be asked which directory you wish to install them to. Typically, this will be c:\jdk1.3.1 if the Java Development Environment you downloaded was version 1.3.1 etc.

To change the base directory/folder of the Java SDK installation you wish to use for compilation purposes, change the directory details in the Base JDK Path: text box. If you wish to select a directory with your mouse, click on the button to the right of the text box, and whichever directory you select will be placed in the text box.

If you right-click over the Base JDK Path: title, then you will see a pop-up menu to choose one of the Java SDK installations that have been auto-detected on your system (must be in either the c:\ or c:\program files directory) , or the latest JDK version installed.

To change the base directory/folder of the Java SDK Documentation installation you wish to use to access from the Help | Java SDK menu, change the directory details in the Bask Docn Path: text box. If you wish to select a directory with your mouse, click on the button to the right of the text box, and whichever directory you select will be placed in the text box.

If you click on the Store environment information with project file? check-box and place a check/tick into the box, then this path information will be stored with the project, overriding and replacing the global path. In general, this is to be avoided, unless you have different project that will be using different versions of the JDK.

The Class Paths method is used to override the CLASSPATH environment variable, which holds a list of paths/directories that have standard classes and libraries of classes. This is normally set up when you install the JDK, but if you wish to override this for your project, you can list a number of directories, one-per-line in this text box. If you wish to include the normal class path in this list as well, then click on the +CLASSPATH check-box.

You can see what the current standard class path is by hovering your cursor over the +CLASSPATH checkbox. A ToolTip will be displayed showing the current class path.

Another way of checking is to click on the button on the Windows task-bar, click on the Run... option and type command (or cmd for Windows NT, 2000 or XP), and click on the OK button. This takes you into the command processor.

Now enter SET CLASSPATH and press ENTER. The contents of the class path will then be displayed. If the result says Environment variable CLASSPATH not defined then the class path has not been defined. This is not vitally important, as a default class path will be ascertained by QuickCup from the java development kit that you have selected.

The Java Command Output Window

If you click on the button on the toolbar, the Command Output Window will be displayed. This shows the results of the various functions that are called from the Java Software Development Kit.

When one of these utilities are invoked, a message tells you which utility is invoked, the directory from which the command is being executed, and the command-line equivalent (i.e. what you would have to type yourself from the command-line to do this same thing).

Anything that follows this, up to the message Process Completed is output from the utility that has been invoked.

In the example shown above, the compiler has been invoked by clicking on the button. There was an error in the source code - the variable blueDirection was incorrect spelled. This took place on line 114, so using the goto button (), the name was corrected, and the compiler invoked again. This time, there was no messages from the compiler, so all was OK.

Note that if the utility was not invoked at all, you can expect there to be no pause or delay whilst the application is running. This may indicate that you have the wrong directory for the Java Software Development Kit.

Quick Function Reference

Click here to view the page contents, if you wish to find a specific function.

Briefly, the functions, categorized by each menu, are listed below, by their menu title:-

File Menu

New Project: If you wish to start a new programming project (i.e. work on a new program), you can create a new program by choosing this option, selecting a directory, and typing in the filename of the project you wish to create. Note that the contents of the currently opened project will be copied to the new project, in case you wish to duplicate its functionality. If you did not, you may wish to close the old project first. All QuickCup project filenames end with the suffix .qjp (abbreviated of QuickCup Java Project).
Note that it is also possible to perform this function simply by typing in a new name into the Project Filename text-box in the Project Properties section, and clicking on another field (or tabbing out of the field).
Note also that you can avoid using the menu, and obtain this function directly from the keyboard by holding down the Ctrl key and pressing the N key.
New File: Add a new file to the project. This will give you a dialog box to select a directory and filename. Typically, the file would be a java source code file, but could be a html or text file.
The file will be added to the Other Java Files list in the Files In Project section.
Note also that you can avoid using the menu, and obtain this function directly from the keyboard by holding down the Ctrl and Alt keys together and pressing the N key.
Alternatively, you can click on the button that appears at the right-hand side of the text box below the list of Other Java Files, and select a directory / file.
Any of these methods will place the filename into the text box. Click on the button to add the file in the text-box to the project. You will be asked if you wish to create the file, in which case a blank text file of that name will be created.
Open Project: Open an existing project file. Select a QuickCup project file (ends with .qjp) using the dialog box that pops up.
Alternatively, you can click on the button to the right of the Project Filename text-box to use a dialog box to navigate to another filename, or you can type the filename to load directly in to the text-box and tab out of the text-box.
Note that you can avoid using the menu, and obtain this function directly from the keyboard by holding down the Ctrl key and pressing the O key.
Open File: Add an existing file to the project. This will give you a dialog box to select a directory and filename. The file will be linked to the project to make it easily accessible. It can be a HTML file (ends with .htm or .html), a Java Source Code file (ends with .java), a text file (ends with .txt) or any other file (not generally editable, but can still be included in the project) - for example, audio files (typically end with .wav and .mid) and graphics files (typically end with .gif and .jpg).
You can also perform this via the keyboard by holding down the Ctrl and Alt keys and pressing the O key.
You can also open a file by typing the filename to add to the project directly into the text box at the bottom of the Files in Project section. Alternatively, you can select the file to add using a dialog box by clicking on the button to the right of the text box.
When you have selected the file you require, click on the button to the left of the text-box to add it to the list of files in the project, shown just above the text-box.
Save All: Save any changes made to the project file, and any files added to the project that have been altered (e.g. java programs and html documents).
You can also perform this via the keyboard by holding down the Ctrl key and press the S key.
You can also click the button on the toolbar to perform this function.
Save Project: If you wish to change any changes made to the project without saving any changes you have made to files attached to the project, select this option.
Save File: If you wish to save any changes made to the currently selected file (i.e. if the file currently being edited/viewed), select this option or via the keyboard, hold down the Ctrl and Alt keys and press the S key. This does not save any other files being edited, nor the project file.
You can tell if a file has been changed, as the tab on the tabbed sheet, use to select the file for editing, is suffixed with an asterisk - e.g. . Once the file has been saved, the asterisk will disappear - e.g. .
Close File: This closes the currently selected file being edited or viewed, so that the tab disappears. The file remains in the project, but is no longer active for viewing/amending.
If you click on the Settings tab and look at the Files in Project section, once a file has been closed, you can see that it no longer has a tick next to it.

If you click in the tick-box next to the file to be edited, the file will be available for editing once again.
You can also close the file by holding down the Ctrl key and pressing the F4 key.
Close All: This closes all of the files currently open for editing/viewing, so that only the Settings tab remains, and so that none of the files attached to the project have ticks next to them. If any of the files have been changed, you will be prompted as to whether you wish to save the file.
Close Project: This option will close all files and clear all of the project details. If the project and/or any attached file details have changed, a dialog box will be displayed to confirm whether the details are to be saved. This option is useful if you wish to create a brand new project, starting from scratch with no details copied from another project.
This option is also available from the keyboard by holding down the Shift and Ctrl buttons and pressing the F4 button.
Transfer to Web Site: Once you have created your application, use this option to transfer the details to your web site. Selecting this option will display the following window:-

The details you fill in here are saved with your project (weakly encrypted), so you can reuse them later. The details on the right describe where to store the details:-
- Web Server Name: The name of the ftp server either as an IP address (e.g. 123.123.123.1) or Universal Resource Locator (e.g. simonhuggins.com).
- Login ID: The login ID to the area on the server where your web site is held.
- Password: The password required to login to the server with the given login name. If login ID is anonymous then this would typically be your email address by convention. Note that the password is not shown on the screen for security reasons.
- Port: This is typically set to ftp to represent the standard FTP port (i.e. 21). If the port is something out-of-the-ordinary, you can type it here.
- Server Directory: This is the directory as an offset of the starting directory into which the files will be placed. For example, if the starting directory was simonh on the server, and html files are kept in a directory called html and the web page on which the files are to be placed is at htpp://www.mywebsite.com/java/examples/index.htm then this box might be set to html/java/examples
- Files to transfer: Click on one of these option to decide which files are to be transferred to the web site:-
  - HTML and Class Files: Any HTML files or the .class files that go with any .java files in the project. Note that the classes in the file must match the filename, or be anonymous inner classes. If you use classes that do not match the filename, they will not be sent.
  - HTML and JAR File: Any HTML files in the project and the .JAR archive file of the same name as the project.
  - HTML file only: Only HTML files in the project.
  - Class files only: Only .class files that go with any .java files in the project.
  - JAR file only: Only the .JAR archive file of the same name as the project.
  - All Project Files: All files added to the project, including any .class files that go with any .java files in the project, and any source files.
  - All Open Project Files: As All Project Files, but only those files that show as being open - i.e. are ticked in the list of attached files.
  - All non-source Files: All files in the same directory as the project file that do not end with .qjp, .java, .txt, .htm or .html - i.e. non-source code files.
  - Project Directory: All files in the same directory as the project file, including the project file itself.
- Transfer now: When you click on this button, the application will attempt to transfer the files to your web server using the FTP file protocol. If you use dial-in access to your web server, it will try to dial-in first. If it cannot access the server within 45 seconds, the process will fail. It is advised under these circumstances to close the dialog box and re-open it, and try again. The blue list box will show the progress of the transfer.
- Cancel: Use this button to close the dialog box without keeping any of the setting changes you may have made to the project.
- Close: Use this button to close the dialog box, keeping any of the setting changes you have made to the project.
Print: If you are clicked in the Settings tab, this will print out details about the project on a single sheet of paper. If you are clicked into any other [source code] tab, the program / text shown under the tab will be printed. Pages are numbered and titled with the filename, and lines are word-wrapped to the width of the page. Multiple copies can be printed.
You can also print by holding down the Ctrl key and pressing the P key, or by clicking on the button on the toolbar.
Exit: Choose this option to close the application.

Edit Menu

Undo: This will undo the last change you made to the text you are working on. Select it again straight afterwards to redo it again. Keyboard shortcut is Ctrl and Z.
Cut: This will copy the currently selected text onto the clipboard and delete the selected text, ready to be pasted (i.e. moved) elsewhere. Keyboard shortcut is Ctrl and X.
Copy: This will copy the currently selected text onto the clipboard, but retain the selected text. The copied text can then be pasted elsewhere. Keyboard shortcut is Ctrl and C.
Paste: This will take the text copied using either the Cut or Copy functions from either the QuickCup or any other Windows application, and place the text at the cursor position, or replace text if it has been highlighted. Keyboard shortcut is Ctrl and V.
Delete: This will remove the highlighted text from the text you are currently working from. It is the equivalent of pressing the Delete button on the keyboard.
Select All: This will select all text in the document, ready for you to cut / copy / delete etc. Keyboard shortcut is Ctrl and A.
Find: Use this function to find specific text within the currently selected file.

Type the text that you wish to find in the edit box - you can use either UPPER or lower case, either will be found (unless you specifcally check/tick the Match Case option). You can also select whether to search down from the current cursor location in the text (to the bottom of the document), or up (to the top of the document). Click on the Find Next button (or just press the Enter key) to find the next occurrence in the text. Note that you can still click on the text you are editing and make alterations to the text whilst the Find dialog is still showing. Click on the Cancel button when you have finished using the Find facility.
Note, you can also view the Find dialog box by holding down the Ctrl key and pressing F, or by clicking on the button on the toolbar.
Replace: Use this function to find specific text in the document you are currently working from, and replace the found text with some other text.

You can use the Find Next button to find the next occurrence (always forwards) of the word typed into the Find what text box, as with the Find dialog. If you wish to replace the currently selected word with whatever is typed in the myTimer box, click on the Replace button. The word will be replaced, and the next occurrence found. Click on the Replace All button to replace all occurrences of the text in the document, from the cursor position onwards.
Note that it is a good idea to keep Match case ticked on, as Java is a case-sensitive language.
To access the replace function using the keyboard, hold down the Ctrl and Alt keys and press the R key. Alternatively, you can click on the button on the toolbar.
Goto Line No: When following instructions to navigate around a source code listing, it is useful to be able to jump to a specific place in the source code. An easy way to do this is to refer to the line number of a particular line of source code - i.e. the top-most line in a listing is line 1, the next line down line 2 etc. Note that if a line wraps around the right-hand margin, this will affect the numbering, so it is best to avoid wrapping around margins if you wish to refer to a listing in this way.
For example, in the TextBurst example, the Java that gets the text to display from the HTML page can be found on line 59 of the TextBurst.java program.
To find out what the current line number is, or to move to another line number, select this option or hold down the Ctrl key and press the G key, or click on the button on the toolbar.

The line number on which the cursor currently resides will be shown in the text box. Type over it to move to another line number, and press the Enter key or click on OK. Alternatively, if you were only looking at the line number, press the Esc key or click on Cancel.

Compile Menu

Compile Project Class File: This will check that the syntax of the class file specified by the Main Java File button on the Settings tab is correct, and generate a .class file (containing Java bytecode, readable by any computer running the Java Virtual Machine) with the same filename as the .java file being compiled. The results of the compilation are displayed in the black Java Command Output Window.
You can also compile this file by pressing the F9 button on the keyboard, or by clicking on the button on the toolbar.
Note that if this does not seem to work, or seems to work without pause, you may not have the correct directory set for the JDK - click here for troubleshooting on this problem.
Compile Current Class File: Alternatively, you can compile the class file that you are currently working on using this option. This may be useful if you know that other source code in your project is incorrect, and you wish to eliminate compiler errors by homing in on the specific file you are working on.
You can also do this by holding down the Ctrl key and pressing the F9 key.
Note that if this does not seem to work, or seems to work without pause, you may not have the correct directory set for the JDK - click here for troubleshooting on this problem.
Allow Deprecated Methods: Click on this to put a tick against the menu item in order to allow the use of classes and methods that have been superseded in later version of Java - for example, if you wish people using older JVMs to use your code without having to download the latest plug-in. Take the tick out again if you want to always make use of the most up-to-date (according to which ever JDK version you are using) methods and classes. Note that this setting is stored with the project file.

Run Menu

Run from Web Page: This will take the parameters passed from the HTML file attached to the project (as shown on the Settings tab in the File in Project section) and apply these to the appropriate class file. This tests the applet within the default web browser, but incurs the overhead of launching the browser, the JVM, and the applet from the JVM. You would typically only use this option in the final stages of testing.
You can also run the applet this way by holding down the Ctrl and Alt keys and pressing the W key, or by clicking on the button on the toolbar.
Run Applet: This will take the parameters passed from the HTML file attached to the project (as shown on the Settings tab in the File in Project section) and apply these to the appropriate class file. The applet is run using the appletlauncher program, which means you do not have to have a web browser present to test your applets, and also means that the applets will run quicker for testing purposes.
You can also access this option by holding down the Ctrl key and pressing the R key or by clicking on the icon on the toolbar.
Run Application: If your java program executes as an application rather than (or as well as) an applet, you can use this option to launch it - the fundamental difference being the inclusion of a main method in an application (and usually the definition and creation of a JFrame to display a window). You will get an error message if you try to launch an applet this way.
You can also access this option by holding down the Ctrl and Alt keys and pressing the R key or by clicking on the icon on the toolbar.

Archive Menu

Archive Jar from Directory: This menu yields two possible menu options. These will take files resident in the same directory as the project file instead of using files that are directly attached to the project. This is suitable if you use one directory per project. The files taken from the directory will then be compressed and placed in a single archive file, which is given the same name as the project, except it has an extension of .jar. This JAR file can be sent to your web site in place of any .class files or other supporting files (e.g. pictures, sounds, data files etc.) in order to keep download times down, and make the process of uploading easier.
- Exclude source code: Use this option if you wish to only include files that are required for running effectively from your web site - i.e. exclude source code files, project files etc. All other files (.class files, pictures and audio files etc.) will be picked up and placed in the JAR file. Note that you can also access this option by clicking on the button on the toolbar.
- Include All: Use this option to include every file in the project directory (except the JAR file itself) in the jar file. This is useful if you wish to make the source code / project details available from your web site in an easily downloadable form. It can then be extracted from within the QuickCup application.
Create JAR file from Project: This menu also yields two possible menu options. These will take files that have been specifically added to the project and compress them into a single JAR file of the same name as the project. This option would be suitable if you were holding more than one project per directory, but is open to various difficulties such as having to attach non-editable files such as images and sound files, as well as .class files that do not match the filename they were generated from.
- Exclude source code: Use this option if you wish to only include files that are required for running effectively from your web site - i.e. exclude source code files, project files etc. All other files within the project (e.g. .class files for attached .java files) will be picked up and placed in the JAR file.
- Include All: Use this option to include every file attached to the project into the jar file. This is useful if you wish to make the source code / project details available from your web site in an easily downloadable form. It can then be extracted from within the QuickCup application.
Extract Files from JAR: Click on this option to select a JAR file and then select a directory that the contents of the JAR file are to go into, and then extract all of the file and place them into that directory. This is useful if you have packaged up your project details into an archive, posted them onto a web site, with the idea of making the file downloadable and extractable as an example java project.
Cleanup class files: This function will delete all files ending with .class in the current project directory. This is useful if you wish to test that a JAR file is working correctly, and that the details are not just being picked up from the .class files in the project directory. To recreate the class files again, just recompile your project.

Help Menu

Help Contents: View global HTML help contents page for the application. This includes copyright and contact details, a history of application changes, functional reference, and tutorials. You need to have a web browser (preferably Internet Explorer) installed on your PC to view these details.
JDK Help: This option is only available if you have installed the Java SDK documentation and stated the base directory location in the Base Docn Path text box on the Settings tab. It gives you quick access to the various HTML pages in the Sun Java SDK documentation, such as command references, tool references, and links to some of the more prominent Java Foundation Classes.
QuickCup Web Site: This launches your web browser and directs you to the QuickCup web site. If you use a dial-up connection and you are off-line, this may also launch the dial-up dialog box. You can access the latest news, product version, instructions and sample files from here.
Sun Java Web Site: This launches your web browser and directs you to the Java Sun web site. If you use a dial-up connection and you are off-line, this may also launch the dial-up dialog box. You can access the latest Java SDK and other product information direct from the makers of Java from here.
Readme text: This will display a scrollable window with textual information about the application, the latest changes, and contact information. It is a useful quick reference for general product details. Click on the Close button to finish reading these details.
Copyright Details: This will display a scrollable window with information about the copyright information that you have agreed to, by using the application. Click on the Close button to finish reading these details.
About: General details about the application - look here to find the version number that you are using, and basic copyright details. You can also launch the web site from here by clicking on the web/email address. Click on the Close button to close this window.

Closing the application

To close the QuickCup application, you can do one of four things:-

Click on the icon at the top-right hand corner of the QuickCup screen with the menu on (not the black Java command output window).
Click on the File menu and then select the Exit menu option.
Press the following combination of keys: Hold down the Ctrl key, hold down the Alt key, and press the X key.
If you are clicked in the QuickCup screen with the menu on (not the black Java command output window), you can use the standard Windows close key-combination: Hold down the Ctrl key and press F4.

If you have made any changes to any of the files, or to the project, you will be asked if you wish to save those changes. Normally you would wish to do so, in which case you would click on the Yes button. However, if you made some changes you do not wish to keep, click on the No button instead. If you change your mind, and you don't wish to quit the QuickCup program after all, click on the Cancel button.

(c) Copyright 2001-2 Arctan Computer Ventures Ltd. All Rights Reserved.
If you have any issues regarding this on-line help, please contact the author by clicking here.
This Page was last updated: 26 April 2002 16:58