Casio fxcp400 fxcp400 User Manual

Page of 275
Chapter 1: Basics
  25
Catalog keyboard configuration
Tapping a letter button displays the 
commands, functions, or other items that 
begin with that letter. 
This is an alphabetized list of commands, 
functions, and other items available in the 
category currently selected with “Form”. 
Tap the down arrow button and then 
select the category you want ([Func], 
[Cmd], [Sys], [User], or [All]) from the list 
that appears.
Tap this key to input the item that is 
currently selected in the alphabetized list.
 
To use the catalog keyboard
Example:  To input the built-in command “Plot”
1. On the catalog keyboard, tap the “Form” down arrow button and then select [Cmd] from the list of categories 
that appears. 
2. Tap the 
+ button in the upper right corner until the P button is visible.
3. Tap 
P.
4. In the alphabetized list, tap “Plot” and then tap [INPUT] to input the command.
• Instead of tapping [INPUT], you could also tap the command a second time to input the command.
1-5  
ClassPad Data
This section provides information about the various types of data that can be stored in ClassPad memory, and 
the location where each type of data is stored. It also explains how to use Variable Manager, which is a tool for 
managing stored data, as well as file operations (file save, recall, delete, rename, etc.) that are common to a 
number of different applications.
 Data Types and Storage Locations (Memory Areas)
ClassPad uses a “main memory” memory area to store various types of data.
Examples:
• Executing “10
x
” (which assigns a value of 10 to variable 
x
) in the Main application or eActivity application 
causes variable 
x
 to be stored in main memory as “EXPR” (expression) type data. 
• Creating a user-defined function (page 196) causes the function to be stored in main memory as “FUNC” 
(function) type data.
• Saving a spreadsheet to a file (by executing [File] - [Save] with the Spreadsheet application) saves the file in 
main memory as “MEM” (memory) type data. 
An eActivity file created with the eActivity is stored in a separate eActivity memory area in order to keep it 
separate from other application data.
Accessing Data
Besides the application that originally created it, data in main memory can also be accessed by any other 
application. It can also be deleted, renamed, copied, moved and otherwise accessed using Variable Manager 
(page 27). eActivity files can be accessed from the eActivity application only.