I ran into an odd bug with printing glyphs. I think what's happening is that if it detects a button glyph being used on a line with a btn() or btnp() function, it replaces all instances of the button glyphs on that line with the appropriate button number. This is a problem if you do something like the following two lines of code (obviously using actual glyphs instead of these unicode chars):
if (btn(⬅️)) print("⬅️") print("❎",20,20,btn(⬅️) and 7 or 5)
The following gif shows the code for the cart above:
It seems to be working for me, both in the embedded player, and my standalone (0.1.11f on Mac OS). I see glyphs in both rows, no numbers.
However, it was interesting to discover that copy/pasting the code from the "code" tray of the embedded player didn't work when pasting into the player. I think because it pasted all the glyphs as (e.g.) \139, and code like btn(\139) was seen as a syntax error.
Maybe the site's embedded player needs to produce the expected unicode now, so pasting into the engine works again?
Possibly the editor should also continue to accept \139 etc as alternative representations still, too.
Log in to post a comment