Gideros 2021.10 released

hgy29 · October 2021

Gideros 2021.10 has just been released!

A few fixes and improvements on this one, yet the biggest addition is the (still beta) Oculus Quest export support. It lacks working hand tracking support, but what you can do with Gideros on Oculus is already impressive. And having a Gideros player right in the headset to test your code live is something that makes Gideros unique.

Documentation about Oculus API isn't published yet, but if you'd like to try for yourself don't hesitate to ask on the forum.

Changes:

New features
[export/oculus] Oculus Quest export support

Improvements
[core] Add application:getNativePath()
[plugin/imgui] Better way to detect modifiers keys (ALT, CTRL, SHIFT, META (SUPER))
[plugin/imgui] 1.84.2 update
[plugin/imgui] Added "IO:loadIniSettings(file_path)"
[TextureBase] Added "getSize" function
[lib/luashader] Handle WebGL2
[desktop/input] Propagate table/pen button to touch event
[core] Effect stack now support automatic buffer resizing
[plugin/reactphysics3d] Add a few missing API calls

Fixes
[plugins/bump] Fixes for some API calls
[plugin/imgui] Fixed "ImGui:pushFont()"
[plugin/imgui] Added "IO:saveIniSettings(file_path)"
[plugin/imgui] Fixed "attempt to call a nil value" issue when using input text OR window resize callbacks
[Sprite] Fixed "Sprite:redrawEffects()"
[qt] Avoid reporting duplicate mouse events for pen events

Download it from here:
http://giderosmobile.com/download

keszegh · October 2021

@hgy29 , with pen pressure i have the same dichotomy:
A ) when 'use windows ink' is set to on in wacom settings then:
1. i get pressure info when using the pen.
2. the touch.mouseButton is always 0, also when i just click the pen button (while hovering) instead of drawing with it, and thus it WRONGLY behaves like a left-click in my imgui items.
B ) when 'use windows ink' is set to off in wacom settings then:
1. i do not get pressure info, more precisely the events are WRONGLY registered as mouse events and not penTablet events.
2. the touch.mouseButton is correctly 1 if i draw and 2 if i click the pen button (while hovering), and thus it behaves like a right-click in my imgui items.

EDIT: i'm happy to test if you can come up with some kind of correction, this issue is really unpleasant since i've spent months on switching to imgui and now a big part of the gui depends on right clicking with the pen button.

keszegh · October 2021

let me copy from the other thread the things which might help:
FIRST:
even more, it seems qt can work with wintab directly or with windows ink, and it is possible to switch between these two options:
https://codereview.qt-project.org/c/qt/qtbase/+/295623
i think now gideros probably uses windows ink. can we switch or even better add this option somewhere? (in project settings or in api)
my guess is that perhaps wintab version would work better, but of course it needs to be tested.
see also
https://github.com/opentoonz/opentoonz/issues/3817
and
https://bugreports.qt.io/browse/QTBUG-83218

SECOND:
https://doc.qt.io/qt-5/qtabletevent.html :
"New in Qt 5.4: QTabletEvent includes all information available from the device, including QTabletEvent::buttons(). Previously it was not possible to accept all tablet events and also know which stylus buttons were pressed."

my guess is that allowing to switch on/off if my app uses wintab or windows ink drivers could be the solution (as i think wintab would work correctly).

keszegh · October 2021

on the positive side the 'double events (penTablet+mouse)' seem to have disappeared indeed, now there is only one of them when drawing, which is quite good (but sadly either a penTablet without button info or a mouse event without pressure info).

hgy29 · October 2021

I am surprised you don't get the button info with penTablet event, as I specifically added it: https://github.com/gideros/gideros/commit/195c156104827408cccfe2b8055cddf1951ce136#diff-b1e17a4a84c0c5738a0e4934521803cde4fe861bc1a2cc60fa6bf07b9114870f

keszegh · October 2021

@hgy29 , perhaps QT does not give the right button info already (And perhaps with wintab driver it would), i don't know.
in any case what i get is something like (when alternately drawing and pressing pen button):
with windows ink:
penTablet pressure: 0.328125 button: 0
penTablet pressure: 0 button: 0
penTablet pressure: 0.1083984375 button: 0
penTablet pressure: 0 button: 0
penTablet pressure: 0.2861328125 button: 0
penTablet pressure: 0 button: 0
penTablet pressure: 0.2509765625 button: 0
penTablet pressure: 0 button: 0

without windows ink:
mouse pressure: 0 button: 1
mouse pressure: 0 button: 2
mouse pressure: 0 button: 1
mouse pressure: 0 button: 2

hgy29 · October 2021

By the way 0 means no button, left button is 1 and right button is 2

keszegh · October 2021

i thought so, thus it is extra strange.

hgy29 · October 2021

Just to be sure, is that on the touch_begin event ?

keszegh · October 2021

yes, it is added as self:addEventListener(Event.TOUCHES_BEGIN, self.onTouch,self)

MoKaLux · October 2021

(at) hgy29, thank you for yet another BIG Gideros release

keszegh · October 2021

hgy29 said:
Just to be sure, is that on the touch_begin event ?

@hgy29 , as this is the main issue which stops me from updating my app to a new major version, let me stick to the topic. i don't know if you have tried the two possible ways i've proposed, if yes, let me know so i can try to find other things. i wish i could be more helpful, so let me know also if i can do something else as well.

hgy29 · October 2021

keszegh said:

hgy29 said:
Just to be sure, is that on the touch_begin event ?
@hgy29 , as this is the main issue which stops me from updating my app to a new major version, let me stick to the topic. i don't know if you have tried the two possible ways i've proposed, if yes, let me know so i can try to find other things. i wish i could be more helpful, so let me know also if i can do something else as well.

I understand your concerns, but the main issue on my side is that I don't have a tablet to test what I could code. I'd rather stick to official API than reliying on wintab (which is a wacom specific DLL according to what I read), but if nothing else works than why not. I will try to report the 'buttons' field in lua (I used the 'button' field in my last change), and if that doesn't help I'll go the wintab way

keszegh · October 2021

thanks, i can try out dll's with my wacom as much as you need.
it seems switching to wintab driver can be done in-app so that could be a lua function to change and thus optional (and windows driver could be default).
overall by what i read so far, in many apps (krita, etc. ) it seems there are also plenty of issues with how windows handles tablets, in particular wacoms, and they end up using wintab in some way or another.

keszegh · October 2021

i've read that not every machine (eg. a microsoft surface laptop) supports wintab so i agree that if we could register button while staying with windows ink would be best. but if this fails, optional wintab support is better than nothing. (also i've read that wintab might be much faster than windows ink, while it can also support tilt etc. that windows ink cannot, so it has other advantages too)

MoKaLux · November 2021

How are you all doing? I have this error on html5.

The accompanying text file contains the whole list (warnings and errors), for information only. I think it is due to imgui?

Thank you and viva Gideros

hgy29 · November 2021

@MoKaLux, do you have a public link to your game ? I'd like to check the stack trace of the exception to be sure which part of gideros is causing it

MoKaLux · November 2021

@hgy29 I re-uploaded it for you to test here https://mokatunprod.itch.io/parallax-bgs

thank you

PS: here is the new log with the new upload

MoKaLux · November 2021

the new file

I cannot upload the txt file

gideros forum error: Cannot use object of type stdClass as array

MoKaLux · November 2021

sorry for the double posts, it wasn't me

hgy29 · November 2021

@MoKaLux thanks, the crash is indeed occuring in imgui plugin, in function BeginDisabled() as far as I can tell know, but I don't understand why yet

MoKaLux · November 2021

I can confirm that now this works

I commented this code:

self.imgui:dummy(28, 28)
-- self.imgui:beginDisabled(0) -- crashes html5
-- self.imgui:dragFloat("speed", 0, 0.001, nil, nil, "%.2f", 0)
-- self.imgui:endDisabled() -- crashes html5

https://mokatunprod.itch.io/parallax-bgs

Maybe it is because of bad argument in self.imgui:beginDisabled(0) although this works on windows!

Please note both beginDisabled and endDisabled crash html5.

Thank you (at)hgy29 for finding the issue

hgy29 · November 2021

Yes, endDisabled() has the same issue. What happens is that the compiler somehow thought those functions never return, while they do. I don't see anything wrong with the code so I'd blame the compiler (llvm). Some people already reported similar issues. Meanwhile maybe we can prevent the compiler to act badly, by rearranging the code a bit. Some similar functions (such as endChild) are compiled correctly.

keszegh · November 2021

so coming from the imgui thread, i realized that gideros does not register hover event when it is done by a wacom pen (and thus e.g. in imgui i cannot show a tooltip if somebody hovers with a pen over the appropriate item). would it be possible to do that?

keszegh · November 2021

hi, when can we expect a new release? i'd want to test the new touch->mouse event thing if it helps me to make imgui work properly with pens. ty

MoKaLux · November 2021

@keszegh I have a feeling it's going to be very soon

https://github.com/gideros/gideros/commit/f0968d749452b511ff35648e9e20494b78019404

keszegh · November 2021

MoKaLux said:
@keszegh I have a feeling it's going to be very soon
https://github.com/gideros/gideros/commit/f0968d749452b511ff35648e9e20494b78019404

speak of the devil. sounds great.

hgy29 · November 2021

Yes, binaries are built, I am uploading them, Windows version should be ready before the end of the day (CET), and Mac version tomorrow perhaps.

keszegh · November 2021

@hgy29 , there is an origin for the mouse event but the pressure info does not seem to be forwarded:
https://wiki.gideros.rocks/index.php/Event.MOUSE_DOWN
or is it? as it is now i cannot replace my touch listeners with mouse listeners even though that would be my attempt at the imgui issues.

keszegh · November 2021

keszegh said:
@hgy29 , there is an origin for the mouse event but the pressure info does not seem to be forwarded:
https://wiki.gideros.rocks/index.php/Event.MOUSE_DOWN
or is it? as it is now i cannot replace my touch listeners with mouse listeners even though that would be my attempt at the imgui issues.

EDIT: ok one can work around this, so i can test if what i want works. but in long term the pressure info should be forwarded too.

keszegh · November 2021

btw 'type' of mouse/touch events is undocumented (i don't mean mouseType or touchType but type (which can be "mouseDown" etc.), even though quite useful.

Howdy, Stranger!

Categories

In this Discussion

Top Posters

Gideros 2021.10 released

Comments

Howdy, Stranger!

Quick Links

Categories

In this Discussion

Top Posters

Gideros 2021.10 released

Comments