FirstRunDialog.3 3.3 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071
  1. .TH "FirstRunDialog" 3 "Tue Aug 9 2022" "openPilotLog" \" -*- nroff -*-
  2. .ad l
  3. .nh
  4. .SH NAME
  5. FirstRunDialog \- The \fBFirstRunDialog\fP is used as a set-up wizard for the application\&.
  6. .SH SYNOPSIS
  7. .br
  8. .PP
  9. .PP
  10. \fC#include <firstrundialog\&.h>\fP
  11. .PP
  12. Inherits QDialog\&.
  13. .SS "Public Member Functions"
  14. .in +1c
  15. .ti -1c
  16. .RI "\fBFirstRunDialog\fP (QWidget *parent=nullptr)"
  17. .br
  18. .in -1c
  19. .SS "Protected Member Functions"
  20. .in +1c
  21. .ti -1c
  22. .RI "void \fBreject\fP () override"
  23. .br
  24. .ti -1c
  25. .RI "void \fBkeyPressEvent\fP (QKeyEvent *keyEvent) override"
  26. .br
  27. .RI "Shows the debug widget by pressing <ctrl + t> "
  28. .in -1c
  29. .SH "Detailed Description"
  30. .PP
  31. The \fBFirstRunDialog\fP is used as a set-up wizard for the application\&.
  32. The Application does not ship with a database, it is created on the fly\&. This is the main purpose of the \fBFirstRunDialog\fP\&. Apart from this main task, user details and preferences are gathered and saved using \fBSettings\fP\&.
  33. .PP
  34. The Dialog contains a tabbed widget which guides the user through the set up process\&.
  35. .SS "1 - Welcome"
  36. In this tab, the user is greeted and has the option to import an existing database instead of creating a new one\&.
  37. .SS "2 - Personal Data"
  38. In this tab, the users personal data is collected, which is used to create the first Pilot Entry in the database\&. ROW ID (1) identifies the logbook owner, which is also referred to as 'self' in the application\&.
  39. .SS "3 - Currencies"
  40. In this tab, the user can enter the expiration dates of his licenses, medical or other currencies that he wishes to keep track of\&. These are stored in the database within the currencies table\&.
  41. .SS "4 - Flight Logging"
  42. In this tab, the user can determine what the defualt selections for logging a new flight will be\&. These selections (Pilot Function, Flight Rules,\&.\&.\&.) are stored in an INI file using the \fBSettings\fP class\&.
  43. .SS "5 - Customization"
  44. In this tab, the user can make selections regarding the application layout and theming, as well as with regards to how data is being displayed\&. These settings are stored in an INI file using the \fBSettings\fP class\&.
  45. .SS "6 - Finish / Database creation"
  46. In this tab the user can select how the database is created\&. There are two options, either downloading database templates from the github repository, or to fall back to a set of JSON files inclnuded in the application ressources (see templates\&.qrc)\&. These built in files are probably not as up-to-date, but enable the application to function if no internet connection is available or the links to the online ressources are broken\&.
  47. .PP
  48. For Debug purcposes, pressing <ctrl+t> will enable a line edit in which a different branch than main can be selected from which the database templates are to be pulled\&.
  49. .PP
  50. Upon successful completion of the \fBFirstRunDialog\fP, a Setting is written so that the dialog is not shown on subsequent runs\&.
  51. .SH "Member Function Documentation"
  52. .PP
  53. .SS "void FirstRunDialog::keyPressEvent (QKeyEvent * keyEvent)\fC [override]\fP, \fC [protected]\fP"
  54. .PP
  55. Shows the debug widget by pressing <ctrl + t> keyPressEvent ctrl + t enables debug mode, showing the branch selector which is used to select a git branch other than main for downloading the templates
  56. .PP
  57. \fBParameters\fP
  58. .RS 4
  59. \fIkeyEvent\fP
  60. .RE
  61. .PP
  62. .SH "Author"
  63. .PP
  64. Generated automatically by Doxygen for openPilotLog from the source code\&.