Crate bitcoin_qt

source ·

Modules

Macros

Structs

  • | Widget that shows a list of sending or | receiving addresses. |

  • | Qt model of the address book in the core. | This allows views to access and modify | the address book. |
  • | Private implementation |
  • | QSpinBox that uses fixed-point numbers | internally and uses our own formatting/parsing | functions. |
  • | Multifunctional dialog to ask for passphrases. | Used for encryption, unlocking, and | changing the passphrase. |
  • | Qt model providing information about | connected peers, similar to the “getpeerinfo” | RPC call. Used by the rpc console UI. |
  • | Bitcoin address widget validator, | checks for a valid bitcoin address. |
  • | Base58 entry widget validator, checks | for valid characters and removes some | whitespace. |
  • | Widget for entering bitcoin amounts. |
  • | Main Bitcoin application object |
  • | Bitcoin GUI main class. | | This class represents the main window | of the Bitcoin UI. | | It communicates with both the client | and wallet models to give the user an | up-to-date view of the current core | state. |
  • | Bitcoin unit definitions. Encapsulates | parsing and formatting and serves as | list model for drop-down selection | boxes. |
  • | Export a Qt table model to a CSV file. | This is useful for analyzing or post-processing | the data in a spreadsheet. |
  • | Model for Bitcoin network client. |

  • | Dialog for creating wallets |
  • | Dialog for editing an address and associated | information. |
  • | Check free space asynchronously to | prevent hanging the UI thread. | | Up to one request to check a path is in | flight to this thread; when the check() | function runs, the current path is requested | from the associated Intro object. | | The reply is sent back through a signal. | | This ensures that no queue of checking | requests is built up while the user is | still entering the path, and that always | the most recently entered path is checked | as soon as the thread becomes available. |
  • | “Help message” dialog box |
  • | Class encapsulating Bitcoin Core startup | and shutdown. | | Allows running startup and shutdown | in a different thread from the UI thread. |
  • | Introduction screen (pre-GUI startup). | | Allows the user to choose a data directory, | in which the wallet and block chain will | be stored. |

  • | macOS-specific Dock icon handler. |
  • | Macintosh-specific notification | handler (supports UserNotificationCenter). |
  • | Modal overlay to display information | about the chain-sync state |
  • | Coin network-specific GUI style information |
  • | Cross-platform desktop notification | client. |

  • | Preferences dialog. |
  • | Interface from Qt to configuration | data structure for Bitcoin client. | | To Qt, the options are presented as a | list with the different options laid | out vertically. | | This can be changed to a tree once the | settings become sufficiently complex. |
  • | Overview (“home”) page widget |
  • | Dialog showing transaction details. |
  • | This class handles payment requests from | clicking on bitcoin: URIs | | This is somewhat tricky, because we have to | deal with the situation where the user clicks | on a link during startup/initialization, when | the splash-screen is up but the main window | (and the Send Coins tab) is not. | | So, the strategy is: | | Create the server, and register the event | handler, when the application is created. Save | any URIs received at or during startup in | a list. | | When startup is finished and the main window is | shown, a signal is sent to slot uiReady(), | which emits a receivedURI() signal for any | payment requests that happened during startup. | | After startup, receivedURI() happens as usual. | | This class has one more feature: a static | method that finds URIs passed in the command | line and, if a server is running in another | process, sends them to the server. |

  • | Qt model providing information about | connected peers, similar to the “getpeerinfo” | RPC call. Used by the rpc console UI. |
  • | Coin network-specific GUI style information |
  • | Proxy address widget validator, checks | for a valid proxy address. |
  • | Label widget for QR code. This image | can be dragged, dropped, copied and | saved to disk. |
  • | Line edit that can be marked as “invalid” | to show input validation feedback. | When marked as invalid, it will get a | red background until it is focused. |
  • | QComboBox that can be used with QDataWidgetMapper | to select ordinal values from a model. |
  • | Class for handling RPC timers (used | for e.g. re-locking the wallet after | a timeout) |

  • | Local Bitcoin RPC console. |
  • | Object for executing console RPC commands | in a separate thread. |
  • | Dialog for requesting payment of bitcoins |

  • | Model for list of recently generated | payment requests / bitcoin: URIs. | | Part of wallet model. |
  • | Dialog for sending bitcoins |
  • | A single entry in the dialog for sending | bitcoins. | | Stacked widget, with different UIs | for payment requests with a strong payee | identity. |
  • | “Shutdown” window |
  • | Class for the splashscreen with information | of the running client. | | ———– | @note | | this is intentionally not a QSplashScreen. | Bitcoin Core initialization can take | a long time, and in that case a progress | window that cannot be moved around and | minimized has turned out to be frustrating | to the user. |
  • | Provide a human-readable extended | HTML description of a transaction. |
  • | Dialog showing transaction details. |
  • | Filter the transaction list according | to pre-specified rules. |
  • | queue notifications to show a non freezing | progress dialog e.g. for rescan |
  • | UI model for a transaction. A core transaction | can be represented by multiple UI transactions | if it has multiple outputs. |
  • | UI model for transaction status. The | transaction status is the part of a transaction | that will change over time. |
  • | UI model for the transaction table of | a wallet. |
  • | Private implementation |
  • | Widget showing the transaction list | for a wallet, including a filter row. | | Using the filter row, the user can view | or export a subset of the transactions. |
  • | Comparison operator for sort/binary | search of model tx list |

  • | Controller between typename NodeInterface, | WalletModel instances and the GUI. |
  • | A container for embedding all wallet-related | controls into BitcoinGUI. | | The purpose of this class is to allow | future refinements of the wallet controls | with minimal need for further modifications | to BitcoinGUI, thus greatly simplifying | merges while reducing the risk of breaking | top-level stuff. |
  • | Interface to Bitcoin wallet from Qt | view code. |
  • | Data model for a walletmodel transaction. |
  • | WalletView class. This class represents | the view to a single wallet. | | It was added to support multiple wallet | functionality. Each wallet gets its | own | | WalletView instance. | | It communicates with both the client | and the wallet models to give the user | an up-to-date view of the current core | state. |

Enums

Constants

Traits

Functions

Type Definitions