kopia lustrzana https://github.com/ctjacobs/pyqso
Re-organised the manual chapters.
Christian Jacobs
rodzic
fd5155c99e
commit
dd2ed4f687
|
|
@ -85,6 +85,7 @@ Running PyQSO with the \texttt{-d} or \texttt{--debug} flag enables the debuggin
|
|||
|
||||
\noindent All debugging-related messages are written to a file called pyqso.debug, located in the current working directory.
|
||||
|
||||
\section{Window layout}
|
||||
|
||||
\section{Creating a new logbook}
|
||||
Logbooks are SQL databases, and as such they must be accessed with a database connection.
|
||||
|
|
@ -96,32 +97,32 @@ To create a connection, click \texttt{Connect to Logbook...} in the \texttt{Logb
|
|||
\end{itemize}
|
||||
Once the database connection has been established, the database file name will appear in the status bar. All logs in the logbook will be opened automatically.
|
||||
|
||||
\section{Log management}
|
||||
\subsection{New log}
|
||||
\chapter{Log management}
|
||||
\section{New log}
|
||||
To create a new log, click \texttt{New Log} in the \texttt{Logbook} menu and enter the desired name of the log (e.g. repeater\_contacts, dx, mobile\_log). This name must be unique. Alternatively, use the shortcut key combination \texttt{Ctrl + N}.
|
||||
|
||||
\subsection{Renaming a log}
|
||||
\subsection{Deleting a log}
|
||||
\section{Renaming a log}
|
||||
\section{Deleting a log}
|
||||
|
||||
\subsection{Importing and exporting a log}
|
||||
\section{Importing and exporting a log}
|
||||
While PyQSO stores logbooks in SQL format, it is possible to export individual logs in the well-known ADIF format. View the log you wish to export, and click \texttt{Export Log} in the \texttt{Logbook} menu.
|
||||
|
||||
Similarly, records can be imported from an ADIF file. Upon importing, users can choose to store the records in a new log, or append them to an existing log in the logbook. To import, click \texttt{Import Log} in the \texttt{Logbook} menu.
|
||||
|
||||
Note that all data must conform to the ADIF standard, otherwise it will be ignored.
|
||||
|
||||
\subsection{Printing a log}
|
||||
\section{Printing a log}
|
||||
Due to restrictions on the page width, only a selection of field names will be printed: callsign, date, time, frequency, and mode.
|
||||
|
||||
\subsection{Filtering by callsign}
|
||||
\section{Filtering by callsign}
|
||||
Entering an expression such as \texttt{xyz} into the ``Filter by callsign'' box will instantly filter out any callsigns beginning with that expression.
|
||||
|
||||
\subsection{Sorting by field}
|
||||
\section{Sorting by field}
|
||||
To sort a log by a particular field name, left-click the column header that contains that field name. By default, it is the \texttt{Index} field that is sorted in ascending order.
|
||||
|
||||
\section{Record management}
|
||||
\chapter{Record management}
|
||||
|
||||
\subsection{New record (QSO)}
|
||||
\section{New record (QSO)}
|
||||
A new QSO can be added by either:
|
||||
\begin{itemize}
|
||||
\item Clicking the `+' button in the toolbar.
|
||||
|
|
@ -130,7 +131,7 @@ A new QSO can be added by either:
|
|||
\end{itemize}
|
||||
A dialog window will appear where you can enter the details of the QSO. Note that the current date and time are filled in automatically.
|
||||
|
||||
\subsubsection{Callsign lookup}
|
||||
\subsection{Callsign lookup}
|
||||
PyQSO can also resolve callsign-related information (e.g. the operator's name, address, and ITU Zone) by querying the qrz.com database.
|
||||
|
||||
Note that users must first supply their qrz.com account information in the preferences dialog window.
|
||||
|
|
@ -139,19 +140,24 @@ Note that users must first supply their qrz.com account information in the prefe
|
|||
\chapter{Toolbox}
|
||||
|
||||
\section{DX cluster}
|
||||
A DX cluster is essentially a server through which radio operators can report and receive updates about QSOs that are in progress across the bands.
|
||||
A DX cluster is essentially a server through which radio operators can report and receive updates about QSOs that are in progress across the bands. PyQSO is able to connect to a DX cluster that operates using the Telnet protocol to provide a text-based alert service. As a result of the many different Telnet-based software products that DX clusters run, PyQSO currently outputs the raw data received from the DX cluster rather than trying to parse it in some way.
|
||||
|
||||
|
||||
PyQSO is able to connect to a DX cluster that operates using the Telnet protocol to provide a text-based alert service. As a result of the many different Telnet-based software products that DX clusters run, PyQSO currently outputs the raw data received from the DX cluster rather than trying to parse it in some way.
|
||||
|
||||
\section{Grey line}
|
||||
The grey line tool can be used to check which parts of the world are in darkness. %The grey line window is updated every 30 minutes.
|
||||
The grey line tool can be used to check which parts of the world are in darkness. The position of the grey line is automatically updated every 30 minutes.
|
||||
|
||||
\section{Awards}
|
||||
The awards data is updated each time a record is added, deleted, or modified.
|
||||
|
||||
Currently only the DXCC award is supported, but additional awards will be added if there is user demand for them.
|
||||
|
||||
\chapter{Preferences}
|
||||
PyQSO user preferences are stored in a configuration file located at \texttt{\textasciitilde/.pyqso.cfg}, where \texttt{\textasciitilde} denotes the user's home directory.
|
||||
|
||||
\section{General}
|
||||
|
||||
|
||||
\section{View}
|
||||
Not all the available fields have to be displayed in the logbook. Users can choose to hide a subset of them by unchecking them in the View tab.
|
||||
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue