Gideros 2021.1 Released - Merry Christmas!

antix

@talis I have a strange feeling that @GriseldaBurroughs is a bot. If not then I'd just say don't bother with Gideros, go with whatever is recommended for the hardware you have. You probably can't go wrong with Unreal Engine.

hgy29

I have uploaded Gideros 2021.1.1, the first (and certainly last) bugfix release of 2021.1. It comes with a few enhencements too: imgui, reactpjhysics3d, shaders, etc.
See the full list on the github download page

MoKaLux

I have some strange bugs with latest gideros 2021.3 RC1.
I have an app using buttons (mouse down, up, hover) which, among other things, have Pixels in them.

In the latest release (2021.3 RC1) my buttons don't capture the correct mouse position. If I click on a button (hittestpoint) it doesn't capture the mouse...

When I use the exact same code but with gideros 2021.2 buttons (with Pixel, text, image, ...) and mouse are captured just fine

What could have happened?

Windows 10, gideros 2021.3 RC1 (not ok) gideros 2021.2 (ok).
PS: I have tried uninstalling reinstalling gideros.

PS2: it may be due to the new Pixel:getAnchorPoint() and Pixel:setAnchorPoint(...) which broke the previous default values?

hgy29

MoKaLux said:

PS2: it may be due to the new Pixel:getAnchorPoint() and Pixel:setAnchorPoint(...) which broke the previous default values?

Good catch, the sprite bounds weren't taking into account the new way of handling setAnchorPoint, which move the local vertices coordinates so that local 0,0 matches desired anchor point. I fixed it my local repo.

PS: You can still use the old setAnchorPoint on Pixel, just call it as Sprite.setAnchorPoint(pixel,x,y).

rrraptor

RenderTarget:clear(0, 1, 0, 0, 1, 1)

Does not work. You have to increase width and height by 1 to make it work.

Probably because of this line:
https://github.com/gideros/gideros/blob/7aba140cb3ccfc92c8df451f4e3a48c585556af5/2dsg/grendertarget.cpp#L61
but idk

hgy29

rrraptor said:

Probably because of this line:
https://github.com/gideros/gideros/blob/7aba140cb3ccfc92c8df451f4e3a48c585556af5/2dsg/grendertarget.cpp#L61
but idk

Yes, most probably, we shouldn't substract 1 but maybe 0.5 or something similar, the idea is that the vertices should span just the texels needed