Hello. I checked out github.com/sussman/rovers-day-out am trying to run with Inform 7 on Linux.
I get error message: ‘Table of Common Color Values (continued)’ is meant to be related to an existing table, but I can’t find one if it is.
Anyone able to reproduce this? Anyone have a few minutes to help figure out how to resolve this? Thank you.
Did you install the versions of the extensions included in the repository?
Yes, installed the 5 included extensions (off the github) as the BUILDME instructed. But this (continued) error still persists.
That looks like something is based on an old version if Glulx Text Effects. What extension is the error from? There’s probably a new version of it somewhere.
I’m seeing now there is more error detail:
The table ‘Table of User Styles (continued)’ won’t work as a continuation, because it contains columns not found in the original ‘Table of User Styles’ .
The old table has columns: window, style name, background color, color, first line indentation, fixed width, font weight, indentation, italic, justification, relative size, reversed.
The new table has columns: style name, justification, obliquity, indentation, first-line indentation, boldness, fixed width, relative size, glulx color.
Something like this? docs.textadventures.co.uk/ifansw … fects.html
A lot of extensions seem broken by Glulx Text Effects change. Is there a way to make Glulx Text Effects and other extensions more backwards compatible so that Glulx colors (Glk styles) aren’t broken in almost all the extensions I try?
For example, today I tried “Include Version 1/130803 of Benchmarking (for Glulx only) by Dannii Willis.” and it fails with the same error I posted back on October 1. “The table ‘Table of User Styles (continued)’ won’t work as a continuation, because it contains columns not found in the original ‘Table of User Styles’ .”
Were column names altered or something? Can some alias system be created to bridge the gap of backwards compatibility so that this problem isn’t encountered so frequently?
The system was reworked (since the original was a bit klugey), so there’s not really a way to get “backward compatibility” without just using the old versions of the extensions.