GP Beta Test Forum

Hi! I think it would be great if we could have inspectors, at least in developer mode. When hunting for bugs it's really hard to know where is a button defined or which actions a menu option invokes. We already have browsers, workspaces and debuggers, it feels kind of natural to add inspectors at so...

Yes, all these screenshots were taken in user mode. It seems it only happens on Linux, same goes for the upside-down blocks and highlights bug.

I'll try the new version later today!

I found out how to reproduce this bug, but apparently it's only happening on GNU/Linux. Create a new project, drag the default morph and drop it so that it is partially outside the stage, then resize the stage. The morph is not clipped by the stage any more and overlaps the top bar. Here's what's ha...

More upside down issues:

Actually, I think it only happens when you duplicate blocks that are embedded in other blocks. If you duplicate the whole stack there is no freezing.

I've worked this out, luckily I've just been given this laptop with a fresh Debian install and I practically had nothing installed in it, so these should be universal steps: # dpkg --add-architecture i386 # apt-get update # apt-get install libc6:i386 libncurses5:i386 libstdc++6:i386 libpangocairo-1....

More feedback from our Tuesday "casual coders": When using the shift+click keyboard input, blocks appear upside-down. Highlight morphs (and only highlights, not the highlighted blocks themselves) also appear upside-down everywhere. As for suggestions, they really missed Scratch's (if touching [color...

I've just been given a new 64b computer at work and I can't seem to get GP to fire up: bromagosa@edutec [ ~/GP/GP-alpha-041 ] %./gp ./gp: 12: ./gp: runtime/linux_gp: not found This is what happens if I try to run linux_gp straight away: bromagosa@edutec [ ~/GP/GP-alpha-041/runtime ] %./linux_gp zsh:...

Hi! Last Tuesday we held the third session of the Programming Clubs at the Citilab, and we began to implement Flappy Bird in GP. Here's a list of bugs we found: If the focus is inside an input and you click on "Go", you can't edit the input contents any more. Before clicking on "Go" you always need ...

I see! I understand now.

My coworker is playing with some simple engine simulations and is using lots of trigonometry for those, that's why he felt he needed these primitives. I'll forward this info to him, thanks!