orderbook_processor.cpp

#include "orderbook_processor.h"
#include <QDebug>

OrderbookProcessor::OrderbookProcessor(Orderbook *engine, QObject *parent)
    : QObject(parent),
      engine_(engine)
{
    // Create two separate timers for different update frequencies
    tradingTimer_ = new QTimer(this);
    guiTimer_ = new QTimer(this);

    // Connect timers to their respective processing slots
    connect(tradingTimer_, &QTimer::timeout, this, &OrderbookProcessor::processTrading);
    connect(guiTimer_, &QTimer::timeout, this, &OrderbookProcessor::processGuiUpdate);
}

// Start both timers with different intervals
// Trading timer: Fast updates for responsive order processing (10ms)
// GUI timer: Slower updates for smooth visual experience (250ms = 4 FPS)
void OrderbookProcessor::startUpdates(int tradingIntervalMs, int guiIntervalMs)
{
    qDebug() << "OrderbookProcessor::startUpdates called with trading interval:" << tradingIntervalMs
             << "ms, GUI interval:" << guiIntervalMs << "ms";

    tradingTimer_->start(tradingIntervalMs);
    guiTimer_->start(guiIntervalMs);
}

// Fast processing for trading engine - handles order matching and execution
void OrderbookProcessor::processTrading()
{
    // This can be used for any fast trading-related processing
    // For now, the orderbook handles its own matching, so this is a placeholder
    // In a more complex system, this might handle order queue processing, etc.
}

// Slower processing for GUI updates - emits snapshots for display
void OrderbookProcessor::processGuiUpdate()
{
    qDebug() << "OrderbookProcessor::processGuiUpdate called";

    // 1. Get the data snapshot from the engine
    OrderbookLevelInfos snapshot = engine_->GetOrderInfos();

    qDebug() << "GUI Update - Bids:" << snapshot.GetBids().size() << "Asks:" << snapshot.GetAsks().size();

    // 2. Emit the signal to notify any connected GUI models
    emit snapshotReady(snapshot);
}