mirror of
https://github.com/MaSzyna-EU07/maszyna.git
synced 2026-10-17 07:29:20 +02:00
366645ef59
What the plan tool was missing was not geometry but the ordinary business of editing: taking a mistake back, dividing what is drawn, and seeing what the next click will do before making it. Cofanie. The document is plain data, so a step is a copy of it. What counts as one step is decided by watching the document - a fingerprint over the tracks, turnouts and catalogue - rather than by dressing every edit with a call: a frame that changes anything opens a step, and the step closes when the drawing settles. That is what makes a drag, or a number typed digit by digit, one step and not thirty, and nothing can be forgotten on the way in. Ctrl+Z / Ctrl+Y; the scene editor listens for the same keys, so it hands them over while the plan has the keyboard. Złącze i wycięcie. `insert_joint` divides whichever element a station lands in and leaves one chain: the ground does not move, the curvature at the new joint is the one that was always there, and the fit reads the chain the same way afterwards. It is refused on a straight, because two straights end to end are one straight and the skeleton will not read that, and under a turnout, which is one piece of geometry on one element. `cut_track` takes a piece out and does leave two tracks - a gap is the ground between them, not a hole in a chain. Przejście rozjazdowe. A turnout may now stand against another one: where it stands is then worked out from that one's frog, not authored, so moving either carries the other with it and a trapez stays shut. The frog has to land on the line leaving the other frog - not on the track's axis, which is 1,469 m further on for a 1:9 - so the station is settled by laying the turnout and walking it along until it does. Drawing is a tool now, not what a click happens to do: until Rysuj is on, a click picks what is under it. With it on, the cursor at the growing end shows the corner and the straight the next click would lay, worked out by the same fit_corner the click itself uses. A chain only grows at a loose end, and the first element of a track is put down by two clicks instead of landing on the plan's zero. Also here: the curvature strip under the panel, pikietaż in the rows and at the cursor, how far the laid axis runs from the clicks it was drawn from, the file format saying which frame and which units it is in (v9), plans chosen from the directory instead of typed, and editor/samples/demo.m0s - two parallel tracks and a trapez - with the generator that wrote it and a test that opens it and demands it lays clean.
51 lines
1.9 KiB
C++
51 lines
1.9 KiB
C++
/*
|
|
This Source Code Form is subject to the
|
|
terms of the Mozilla Public License, v.
|
|
2.0. If a copy of the MPL was not
|
|
distributed with this file, You can
|
|
obtain one at
|
|
http://mozilla.org/MPL/2.0/.
|
|
*/
|
|
module;
|
|
#include <optional>
|
|
#include <string>
|
|
|
|
export module eu07.editor.plan_document_io;
|
|
export import eu07.editor.plan_model;
|
|
|
|
export {
|
|
|
|
namespace editor::plan::io {
|
|
|
|
/// The `.m0s` format, version 3.
|
|
///
|
|
/// Line-oriented text, one concept per token, every reference by id, and an
|
|
/// explicit version on the first line. Earlier versions are not read: they
|
|
/// described different models — anchored straights with mode-tagged fits between
|
|
/// them (1), then elements whose lengths were solved against construction lines
|
|
/// (2) — and translating either would have meant keeping those concepts alive in
|
|
/// the reader after they were removed from everything else.
|
|
///
|
|
/// Doubles go through std::to_chars/from_chars, so a round trip is exact and
|
|
/// does not depend on the locale.
|
|
[[nodiscard]] std::string serialize(const plan::Document& document);
|
|
|
|
/// Returns nothing when @p text is not a version 3 document or is malformed.
|
|
[[nodiscard]] std::optional<plan::Document> deserialize(const std::string& text);
|
|
|
|
/// Where plans live: `editor/plan.m0s`, relative to the working directory — which
|
|
/// for the simulator is its own data directory, beside `scenery` and `dynamic`.
|
|
[[nodiscard]] std::string default_project_path();
|
|
|
|
/// The file a name means. A name with no directory in it is a plan, so it belongs
|
|
/// where plans live; anything else is taken as given. Use it to say where a plan
|
|
/// went, or came from, without guessing.
|
|
[[nodiscard]] std::string project_file(const std::string& path);
|
|
bool save(const plan::Document& document, const std::string& path = default_project_path());
|
|
[[nodiscard]] std::optional<plan::Document> load(
|
|
const std::string& path = default_project_path());
|
|
|
|
} // namespace editor::plan::io
|
|
|
|
} // export
|