Maps instrument families and specific trade type codes to form widget factories. More...
#include <InstrumentFormRegistry.hpp>
Collaboration diagram for InstrumentFormRegistry:
Public Types | |
| using | product_type = ores::trading::domain::product_type |
| using | Factory = std::function< IInstrumentForm *(QWidget *parent)> |
Public Member Functions | |
| void | registerForm (product_type pt, QString displayName, Factory factory) |
| bool | contains (product_type pt) const noexcept |
| IInstrumentForm * | createForm (product_type pt, QWidget *parent) const |
| QString | displayName (product_type pt) const |
| std::vector< product_type > | registeredTypes () const |
| void | registerTypeForm (const QString &trade_type_code, Factory factory) |
| Register a dedicated form for a single trade type code. | |
| bool | containsTypeForm (const QString &trade_type_code) const noexcept |
| IInstrumentForm * | createTypeForm (const QString &trade_type_code, QWidget *parent) const |
| std::vector< QString > | registeredTypeCodes () const |
| All registered type codes, in registration order. | |
Detailed Description
Maps instrument families and specific trade type codes to form widget factories.
Two registration tiers:
- Per product-family (product_type): one form handles all sub-types in that family (e.g. BondInstrumentForm covers all bond variants).
- Per trade-type-code (QString): a dedicated form handles exactly one sub-type (e.g. FxVanillaOptionInstrumentForm for "FxOption").
TradeDetailDialog looks up by trade-type-code first, falling back to the family form when no type-specific registration exists.
