I’m testing a gblorb for Spring Thing;
I thought id get the latest interpreter from Ifarchive.
Is there one that I can scroll back up when it goes off the top of the screen. I’m shocked that this doesn’t work. Surely not much to ask?
Experience so far:
Glulxe crashed first time run, then worked. no error printed
Git crashed first time run, then worked. no error printed
lectrote ;
I use Gargoyle, and that scrolls up just fine.
Yeah, likewise, though pretty sure Lectrote allows for scroll back too - actually I think it’s pretty standard across interpreters, so if that’s not working and you’re getting crashes, I wonder whether something might be off with the game file?
Edit: also there often isn’t a scroll bar - you just type page up to go back.
In the Windows versions of Glulxe and Git, you can access the scrollback by pressing CTRL + L or by clicking the small scroll icon (or via the menu bar → Glulxe/Git → Scrollback). It’s a bit inconvenient.
In Lectrote, you can open the Electron/Chromium Developer Tools via the menu (Window → Toggle Developer Tools) or by pressing CTRL + SHIFT + I. Maybe the dev tools console will give an indication why Lectrote seems to have problems with the game.
ok thanks. @DeusIrae there is no pageup in glulxe and lectrote wont run it. Perhaps there’s a problem with the game file. After all, it’s not finished.
Anyhow, i’m having more success with Gargoyle. Although the fonts are too small. It has no built in settings, but it appears you can edit a .ini file.
I’d like to change the font size. You can do this, but then the lines are all squashed together. It appears you have to also set the leading and baseline values. I’ve hacked around and got something working, but how to set the defaults? Do they expect people to somehow know the internal font metrics??
Perps in question:
monofont Gargoyle Mono
monosize 12.6
propfont Gargoyle Serif
propsize 14.7
wmarginx 20 # space around the window frame
wmarginy 20
wpaddingx 0 # space between windows
wpaddingy 0
wborderx 0 # border line width between windows
wbordery 0
tmarginx 7 # internal margin of text windows
tmarginy 7
leading 20 # Also known as linespacing
baseline 15 # Offset from top of line to baseline
commenting them out doesn’t work nor does setting to zero…
Note that many interpreters don’t have their latest version in the IFArchive. The best way to find the latest version will be checking where IFWiki says to download it from.
If the interpreters are crashing then either there’s a bug in the interpreter, or in your storyfile. Please remember to post the interpreter version number you’re using, so then people will know if it is the current version or not.
If by “glulxe” you mean Windows Glulxe, I think it has a separate history/scrollback window.
It does. That’s what I use. Click the Scrollback button (it looks like a scroll), then you can scroll up and down using the scroll bar, mouse wheel or PgUp/PgDn buttons on the keyboard.
Ah. ok.
Directed from IFWiki, I got Lectrote 1.4.5. Doesn’t work.
[2776:0320/123811.157:ERROR:network_change_notifier_win.cc(221)] WSALookupServiceBegin failed with: 0
[2972:0320/123811.816:ERROR:network_change_notifier_win.cc(221)] WSALookupServiceBegin failed with: 0
[2776:0320/123812.057:ERROR:gpu_process_host.cc(937)] GPU process launch failed: error_code=18
[2776:0320/123812.144:ERROR:gpu_process_host.cc(937)] GPU process launch failed: error_code=18
[2776:0320/123812.153:ERROR:gpu_process_host.cc(937)] GPU process launch failed: error_code=18
[2776:0320/123812.170:ERROR:gpu_process_host.cc(937)] GPU process launch failed: error_code=18
[2776:0320/123812.183:ERROR:gpu_process_host.cc(937)] GPU process launch failed: error_code=18
[2776:0320/123812.190:ERROR:gpu_process_host.cc(937)] GPU process launch failed: error_code=18
[2776:0320/123812.207:ERROR:gpu_process_host.cc(937)] GPU process launch failed: error_code=18
[2776:0320/123812.244:ERROR:gpu_process_host.cc(937)] GPU process launch failed: error_code=18
[2776:0320/123812.246:ERROR:gpu_process_host.cc(937)] GPU process launch failed: error_code=18
[2776:0320/123812.246:FATAL:gpu_data_manager_impl_private.cc(440)] GPU process isn't usable. Goodbye.
Ok, this appears to be Electron
What you need is to run with option, either
--in-process-gpu--disable-gpu-sandboxWhat larks!