Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A couple of issues with text and graphics display #43

Open
uecasm opened this issue May 15, 2020 · 3 comments
Open

A couple of issues with text and graphics display #43

uecasm opened this issue May 15, 2020 · 3 comments

Comments

@uecasm
Copy link

uecasm commented May 15, 2020

https://www.mirality.co.nz/if/glulxetest/

This contains a couple of demos of problems I've noticed when using Quixe.

  • demo1 : this tries to display a centred image in a text window. The image does appear, but not centered.
  • demo2 : this tries to use glk_window_move_cursor to then write some text to a specific position in a text grid window. The text doesn't appear at all.

Both of these demos work as expected if you run the blorb file through another Glulx interpreter, such as Git, or the Inform IDE built-in one.

The complete source text is also included on that page so you can see what it's trying to do.

(I also had a problem with images not displaying at all at first, since the IDE release process doesn't set up the loose files that Quixe wants for that. But after some hunting around I found the script for that.)

@uecasm
Copy link
Author

uecasm commented May 15, 2020

Hmm. Interestingly it appears that demo2 does work as expected if I use the version from master instead of the Quixe-217.zip Inform template package. I'm not sure why.

@uecasm
Copy link
Author

uecasm commented May 15, 2020

Ok, I think I've figured out demo2. The issue is that for some reason when using the Inform template package it generates an extra window-refresh event, which was clearing the window since I was just drawing directly into the window rather than making a refresh rule. I'm not sure why the other template and other interpreters don't show this, but I can work around it.

Any ideas on demo1? I assume this is because Quixe doesn't implement "style support". Are there any workarounds?

@uecasm
Copy link
Author

uecasm commented Jul 9, 2020

I've added a demo3 command now, which demonstrates a worse issue that locks up the interpreter due to constant layout switching. I've also included an option to play in either Quixe or the new Parchment build that uses Quixe; interestingly they don't have identical behaviour -- compare demo2 and demo3 in each in particular.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant