Malte Langkabel
648241ba2a
REQ-BLD-COPY-CONFIG is dropped: Shift+right-click no longer caches a building's recipe / schematic+layout / splitter filters, Shift+left-click no longer stamps them onto same-type buildings, and the cyan eligible- target tint and copy/paste flashes go with them. Shift+left-click now falls through to normal selection, which needs no code of its own -- only Ctrl is meaningful to selection (REQ-UI-MULTI-SELECT), so dropping the branch that consumed the click is enough. readBuildingConfig stays. It had two callers, and the other one is captureBlueprintFromSelection, which needs it to record each blueprint building's configuration (REQ-UI-BLUEPRINT-STORAGE). Its five tests stay too, retagged [blueprint] and rewritten to name the caller that is left. The visuals.toml copy_config colour is removed together with its VisualsConfig field and its loader line: overlay keys are mandatory, so those three have to move as one or startup aborts. REQ-BLD-COPY-CONFIG-FEEDBACK, cited by four of these files and by the TOML comment, never existed in requirements.md; deleting the citations retires a dangling id. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JcReq7hVk4KUPhTDKWAG7K
79 lines
3.4 KiB
C++
79 lines
3.4 KiB
C++
#pragma once
|
|
|
|
#include <optional>
|
|
#include <string>
|
|
#include <vector>
|
|
|
|
#include "Blueprint.h"
|
|
#include "BuildingId.h"
|
|
#include "BuildingType.h"
|
|
#include "ItemType.h"
|
|
#include "ShipLayout.h"
|
|
|
|
class Simulation;
|
|
struct BuildingsConfig;
|
|
|
|
// The user-configurable settings of a single building or construction site: the
|
|
// selected recipe / ship schematic, the shipyard module layout, and (for
|
|
// splitters) the two output filters. This is what blueprint capture records per
|
|
// constituent building (REQ-UI-BLUEPRINT-STORAGE).
|
|
struct BuildingConfig
|
|
{
|
|
BuildingType type = BuildingType::Miner;
|
|
|
|
// Selected recipe (Miner / Assembler) or ship schematic id (Shipyard); unset
|
|
// when nothing is selected.
|
|
std::optional<std::string> recipeId;
|
|
|
|
// Shipyard module layout (REQ-MOD-LAYOUT).
|
|
std::optional<ShipLayoutConfig> shipLayout;
|
|
|
|
// Splitter output filters (empty = accept all). isSplitter distinguishes an
|
|
// empty-filter splitter (a valid accept-all configuration) from a building
|
|
// type that has no splitter filters at all.
|
|
bool isSplitter = false;
|
|
std::vector<ItemType> splitterFilterA;
|
|
std::vector<ItemType> splitterFilterB;
|
|
};
|
|
|
|
// Reads the current configuration of the building or construction site identified
|
|
// by id, handling operational buildings and sites alike. Returns std::nullopt if
|
|
// no such building or site exists.
|
|
std::optional<BuildingConfig> readBuildingConfig(const Simulation& sim, BuildingId id);
|
|
|
|
// Captures a blueprint from a selection of building / construction-site ids, keeping
|
|
// only player-placeable buildings and recording each one's type, rotation, offset
|
|
// from the selection's bounding-box center, and configuration. Operational buildings
|
|
// and construction sites are treated identically (REQ-UI-BLUEPRINT-CREATE,
|
|
// REQ-UI-BLUEPRINT-STORAGE). The returned blueprint is unnamed.
|
|
Blueprint captureBlueprintFromSelection(const Simulation& sim,
|
|
const std::vector<BuildingId>& selectedIds);
|
|
|
|
// True if any selected id refers to a player-placeable building or construction site
|
|
// (the condition under which Ctrl+C opens the blueprint save dialog,
|
|
// REQ-UI-BLUEPRINT-CREATE).
|
|
bool selectionHasPlaceableBuilding(const Simulation& sim,
|
|
const std::vector<BuildingId>& selectedIds);
|
|
|
|
// One "<building name> x <count>" entry of a blueprint card's contents line
|
|
// (REQ-UI-BLUEPRINT-CARD).
|
|
struct BlueprintContentEntry
|
|
{
|
|
std::string buildingName;
|
|
int count;
|
|
};
|
|
|
|
// Summarizes what a blueprint holds: one entry per building type it contains, ordered
|
|
// by descending count with ties broken by the order the types appear in buildings.toml
|
|
// (which is the order of the build button bar, REQ-UI-BUILD-BAR). Building types absent
|
|
// from the config sort last. Derived display data for the blueprint card, kept here so
|
|
// it is unit-testable rather than buried in the dialog (REQ-UI-BLUEPRINT-CARD).
|
|
std::vector<BlueprintContentEntry> summarizeBlueprintContents(
|
|
const Blueprint& blueprint, const BuildingsConfig& buildings);
|
|
|
|
// Plain sum of the placement cost of every building in the blueprint
|
|
// (REQ-UI-BLUEPRINT-CARD). Distinct from the total charged on placement
|
|
// (REQ-UI-BLUEPRINT-PLACE), which additionally excludes locked building types and
|
|
// rotate-in-place targets; see GameWorldView's placement path.
|
|
int computeBlueprintCost(const Blueprint& blueprint, const BuildingsConfig& buildings);
|