From e8f4b4016b8dff8dc56c53db9a7eca2e126e35c2 Mon Sep 17 00:00:00 2001 From: Myk Taylor Date: Thu, 5 Nov 2020 16:18:33 -0800 Subject: [PATCH] reinforce that meta blueprints can't cross files they must refer to labels that are within the same .xlsx or .csv file --- docs/guides/quickfort-user-guide.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/guides/quickfort-user-guide.rst b/docs/guides/quickfort-user-guide.rst index f8061b766..5ab0956f7 100644 --- a/docs/guides/quickfort-user-guide.rst +++ b/docs/guides/quickfort-user-guide.rst @@ -1015,6 +1015,11 @@ a big fort, so we're planning for a lot of bedrooms): Note that for blueprints without an explicit label, we still need to address them by their auto-generated numerical label. +It's worth calling out that ``#meta`` blueprints can only refer to blueprints +that are defined in the same file. This means that all blueprints that a +``#meta`` blueprint needs to script must be in sheets within the same +.xlsx spreadsheet or concatenated into the same .csv file. + You can then hide the blueprints that you now manage with the ``#meta``-mode blueprint from ``quickfort list`` by adding a ``hidden()`` marker to their modelines. That way the output of ``quickfort list`` won't be cluttered by