Closed GoogleCodeExporter closed 9 years ago
yes of course, go ahead.
Original comment by esteban....@gmail.com
on 4 Apr 2011 at 3:05
Original comment by ifr...@gmail.com
on 4 Apr 2011 at 3:15
Attachments:
It is illegal according to the glk spec to print to a window which has a
pending line or character input request. You should cancel the request before
printing output, and then re-request after.
This is I believe why the text isn't getting printed.
The spec doesn't say what an interpreter should do when a game tries to print
anyway, and Gargoyle and glkterm (which is what I initially based Frotz's glk
support on) ignore the output. I may go ahead and make it print anyway,
because yours isn't the only game I've run into to make this mistake.
If you get a chance to try out the cancel suggestion, please let me know if it
works.
Original comment by spath...@gmail.com
on 24 May 2011 at 6:41
I've made Frotz print anyway and auto-cancel the input request when this
happens.
This makes the game work, although you still should fix the source.
Original comment by spath...@gmail.com
on 9 Jun 2011 at 11:42
Original comment by spath...@gmail.com
on 9 Jun 2011 at 11:42
To re-request line event in main window:
(- glk_request_line_event(gg_mainwin, buffer + WORDSIZE, INPUT_BUFFER_LEN - WORDSIZE, buffer-->0); -)
To cancel line input in the/-- main-window:
(- glk_cancel_line_event(gg_mainwin, gg_event); buffer-->0 = gg_event-->2; -)
source:http://www.intfiction.org/forum/viewtopic.php?p=8116#p8116
it works well although there is some problem with Gargoyle about it : each time
i cancel/re-request the line input, a newline char gets printed. (other terps
are fine). mmhh ...
Anyway thanks for getting involved in that particular problem.
Original comment by esteban....@gmail.com
on 10 Jun 2011 at 11:55
Original issue reported on code.google.com by
ifr...@gmail.com
on 3 Apr 2011 at 8:53