Gideros Update 2015.12

hgy29 · January 2016

Release 2015.12 is finally out!

Download:
https://github.com/gideros/gideros/releases/tag/2015.12

Changelog:
Added Path2D class and example project
Added CFBundleName for MacOSX export
Added app category for MacOSX export
Fixed touch pressure scaling (values should be between 0 and 1)
Fixed iOS/Apple TV Macros affecting Alert dialogs and other stuff
Fixed JNI errors in notification and googleplay Android plugins
Fixed crash on exit
Fixed iOS notification plugin for iOS8+
Fixed Catching lua errors within event handlers for suspend/resume/resize
Fixed encryption working in bitcoded apps (ios, tvos)
Fixed Windows 10 crash on start
Fixed Windows 10 resizing issue
Studio console search results are displayed on contrasting color

Warning: provided luasocket lib for AppleTV in this release is wrong. A replacement lib can be found here:
http://hieroglyphe.net/gideros/libluasocket.a

vitalitymobile · January 2016

Awesome! Thank you so much!

keszegh · January 2016

thanks, good news.

chuz0 · January 2016

Thanks a lot ! The .svg parser is working great.

keszegh · January 2016

and the path2d seems to be antialiased? i will need to try to change my current antialiased mesh 'engine' to this path2d solution, looks interesting.

hgy29 · January 2016

Path2D outline will be antialiased, but fill won't due to GL ES shaders limitation. Thats a pity because I made it work on desktop.

keszegh · January 2016

and if outline is the same color as the fill?

i got that line cannot be textured though so a textured outline-less path cannot be antialiased in this case.

hgy29 · January 2016

yes, if outline is the same color as the fill and you don't use translucency, then you will get antialiased filled shapes.

Texturing is not yet supported as far as I remember my own code...

keszegh · January 2016

i see, so for now i cannot change but i will experiment with it, and hope that texturing will be supported later (and antialiasing of the fill shape on desktop, if that's possible) as my engine does not support curves so the drawings in my drawing app are always polygonal, which is not optimal.

keszegh · January 2016

guys, i have been waiting a lot for the pressure sensitivity to work on windows, but it's still not ok. (i'm using win10 if that matters)
1. in desktop player there is no registering of my wacom pen pressure at all.
2. in desktop export it is sort of random what is registered, but mostly 0. i attach an example where i pressed the pen like hell and still only sometimes did it register it above zero (the width corresponds to pressure).
3. android i could not test yet.
any ideas?

ar2rsawseen · January 2016

can you print out the pressure values?

And you want to say that your wacom does not work in player but works in export?

keszegh · January 2016

@ar2rsawseen, that was useful, in fact the pressure is always 0 or 1. e.g. after drawing a curve similar to the one above i got:
[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,1,0,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,0,1,1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,1,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,1,1,0,0,0,1,0,0,0,0,0,0,0,1,0,1,0,0,0,1,0,0,0,0,0,1,0,0,1,0,0,0,0,1,0,0,0,0,1,0,0,0,0,0,0,1,0,0,0,1,0,0,0,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,1,0,0,1,1,1,0,0,0,0,0,0,0,1,1,0,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,1,0,0,0,1,0,0,1,0,0,0,1,0,0,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0,1,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,0,0,0,0,1,0,0,0,0,1,1,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1,0,1,0,0]

keszegh · January 2016

in fact in the previous version i had the same problem (it was also 10000 smaller values but the main problem was that it was either 0 or max, only two values), except that now the gplayer has no pressure at all, only exported app gets 0/1 values. but earlier in the players that tkhnoman shared on the forum it was working ok, so i guess it should work, there is probably some integer/rounding bug.

Xman · January 2016

Good job

Xman · January 2016

great

hgy29 · January 2016

main.lua:20: attempt to call method 'setSvgPath' (a nil value)

On which platform did you get that ?

ar2rsawseen · January 2016

@keszegh so it is a wacom specific, that it does not provide range but only 0 or 1?

Btw, can you point to that discussion with @tkhnoman player? I want to make sure his changes are integrated in the repo.

Xman · January 2016

main.lua:20: attempt to call method 'setSvgPath' (a nil value)
On which platform did you get that ?

sorry,just forgot to reinstall my player.I have edited my post in the first time.

keszegh · January 2016

@ar2rsawseen, it is on my wacom, yes. i have no other tablet around, but wacom is the most common brand i guess. is that what you meant by specific?
on my android tablet the pen is not working currently, so i cannot test, i will get a battery and let you know if that works fine.

NatWobble · January 2016

@hgy29 Great, thanks. I love the path2D vectors.
A few minor issues I noticed with the windows player:
1) The fill color was always white when drawing a rectangle clockwise but I could set the colour when drawing anti-clockwise (when I reversed all the vertices).
2) Using setConvex(true) I couldn't set the fill colour at all.

hgy29 · January 2016

@NatWobble, thanks for reporting, I'll fix those ASAP.

tkhnoman · January 2016

@ar2rsawseen I believe the code is integrated, but in the past i used integer and that multiple by 10000 and 0.0001 because i'm afraid float conversion goes wrong.
[This is also based on experience that pressure sensitivity above 4096 is kind of useless, so 10000 is high enough]

Not sure how the codes now, Gideros Player goes error since Qt changed to 5.5 for me, so i did not update at all since 2015.08

keszegh · January 2016

@ar2rsawseen, the conversation with @tkhnoman is here:
http://giderosmobile.com/forum/discussion/5870/new-desktop-api-test#Item_3

btw when i made my android pressure sensitivity plugin i've also sent an integer between 1-100 to gideros from java rather then sending the float value as i had problems with that.

ar2rsawseen · January 2016

I see @keszegh it could be the same problem, so it converts it to integer at some point and only values above 0.5 become as 1, will need to recheck that

totebo · January 2016

About "Fixed iOS/Apple TV Macros affecting Alert dialogs and other stuff"; I've just tried this code on 2015-12 which still doesn't bring up a dialogue box (it works on 2015-09).

local textInputDialog = TextInputDialog.new("Name please!", "", self.player_name, "Go!", nil)
textInputDialog:show()

Do I need to update something else (apart from Gideros) for it to work?

NatWobble · January 2016

@hgy29 I'm getting a few problems with hit point detection using 2Dpath. I think it stems from some issues with getWidth() and getHeight(). I'm getting strange values for a simple rectangle:

 width=131
 height=172
 local vect = Path2D.new()
  local ms="MLLLLZ"     
  local mp={
        0,0,
        0,height,
        width,height,
        width,0,
        0,0
          } 
    --vect:setConvex(true)
    vect:setPath(ms,mp) --Set the path from a set of commands and coordinates
    vect:setLineThickness(stroke) -- Outline width
    vect:setFillColor(fillColor,fillAlpha) --Fill color
    vect:setLineColor(strokeColor,strokeAlpha) --Line color
    vect:setAnchorPosition(0,0)
    vect:setPosition(x, y)
    parent:addChild( vect )

Sometimes the width and height values are 0, sometimes tiny (e.g. 1.875,
4.2038953929745e-045). After tweening the scale back to 1 the values get really inconsistent. I am creating a grid of identical cards that worked fine with images but return different height and width values with the 2Dpath.

ar2rsawseen · January 2016

@totebo unfortunately I think that is different problem.
Currently due to recent changes, ios uses different classes for dialogs, based on what ios version you have.

So what ios version are you using?

totebo · January 2016

@ar2sawseen I'm using the latest one, I think it's 8.1?

hgy29 · January 2016

@NatWooble, sorry for that! Bounds are in fact not computed at all in 2015.12 version. I've fixed that since then.

keszegh · January 2016

@ar2rsawseen , could you find/correct the problem with pressure sensitivity?

ar2rsawseen · January 2016

Currently in the company I work at, we have a major release this month, so not in near time, but after that I will check out what is the problem

Howdy, Stranger!

Categories

In this Discussion

Top Posters

Gideros Update 2015.12

Comments

Howdy, Stranger!

Quick Links

Categories

In this Discussion

Top Posters

Gideros Update 2015.12

Comments