![]() |
JSwat ProjectSettings |
As a JSwat user you may be wondering where it saves the settings
that are created while using the program. There are several groups
of settings, all of which are saved to a directory called
.jswat
in your home directory. These settings are
briefly described below.
The current breakpoints are saved to a file called
breakpoints
in the JSwat settings directory (described
above). This file is a serialized version of the breakpoint objects
and cannot be read or edited easily.
Session properties are settings that relate to the session and
are used by the JSwat actions and commands to persist information
for the next time they are needed. These include the name of the
class being debugged, whether the debuggee VM starts up suspended,
and the options passed to the debuggee VM. The settings are stored
in the session
file in the JSwat settings directory
(described above). This file is a standard Java properties file and
is humanly editable.
These settings effect the application as a whole, such as the
size and position of the main window and the look and feel. These
are stored in settings
in the JSwat settings directory
(described above). This file is a standard Java properties file and
is humanly editable.
These are your user preferences that you set through the
Preferences dialog or options
command. These are
stored in preferences
in the JSwat settings directory
(described above). This file is a form of GML (Graph Modeling
Language) and is humanly editable, assuming you understand GML.
Some of the settings in JSwat are only temporary for the life of the program. These are not saved to any file although they last long enough to be useful while running JSwat. These settings include: