Home › SinisterSoft › Comments
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
SinisterSoft
About
- Username
- SinisterSoft
- Joined
- Visits
- 2,503
- Last Active
- Roles
- Maintainer
Comments
-
Yes, that was added. Nice ehh?
-
I've no idea. Strange.
-
Off on a tangent, the 'missing purpose' thing reminded me of Nathan's 'special purpose' in The Jerk...
-
Was your Zuobox games created using Gideros?
-
I'll write one for Lua Plugins, I've been meaning to do that for a while.
-
No, don't use the old export - just use the new one and untick the generate apk.
-
@MoKaLux You can still do it that way, just untick 'generate apk' in the export option.
-
I haven't noticed any difference in the fonts. @dreiko65 can you post a project somewhere that demonstrates what you mean?
-
Or do you mean one event function for different types of events - like this: function mouse(e) if e.type=="mouseDown" then -- here just mouse down elseif e.type=="mouseUp" then -- here mouse up else -- here everything else end -- this bit…
-
How much does HarfBuzz increase the size by? Will it be needed only for Arabic text? Will BiDi be added to the normal text system too? If so, will the existing ArabicProcessing function still work?
-
@MoKaLux Does @hgy29 's latest arabicProcessing (above) function have the vowel changes you made? If not, could you add them and repost it here?
-
yes, I'll delete him and his comments.
-
I just add virtual pad as the last thing to the stage, then hide it or reveal it.
-
As above, but could be written as: coords={{x=0,y=100},{x=100,y=100},{x=100,y=0},{x=0,y=0}} or simply coords={{0,100},{100,100},{100,0},{0,0}} with coords[1][1] being 0 and [1][2] being 100
-
The api has changed so the plugin may need to be recoded slightly then recompiled - so I'm not sure. The version number grabbed will also need to be updated in the gplugin file - you could start with that and see if it retains compatibility someho…
-
Yes, that works great too. I usually use this method, but inline. Bump has a few advantages as it calculates the rebound and the actual collision point - even if an object is travelling faster than the size of the collision square.
-
Gideros has a plugin for a C version of Bump - it does this sort of collision detection (and more) and may be faster - you should take a look. http://wiki.giderosmobile.com/index.php/Special:MyLanguage/bump Here is the official Bump documentation:…
-
amazon
-
Amazon, google and iOS are the only valid billing systems now I think.
-
yes, sorry about that mixup. I thought it was best to have the texture so it could be used for other things as well as the virtual joypad, etc...
-
I think they have updated their api, so the plugin will need updating. That may fix it.
-
Ahh, I remember I fixed it so you preload the texture (so you don't waste a whole texture on one thing) - the docs will need updating for that. do this: texture=TexturePack.new("gfx/UI/TNTVirtualPad256.txt","gfx/UI/TNTVirtualPad256.png",true) vPad…
-
Here are the current instructions to get you started. https://www.dropbox.com/s/t4kuc31hgo23ztp/tntpad.pdf?dl=0
-
That will be the filename of a packed image file with these images in it: https://www.dropbox.com/s/u4sedv1eplgu1ym/tntpadgfx.zip?dl=0 eg tntskinpad.png & tntskinpad.txt generated from the gideros texturepacker.
-
Looks like @hgy29 made Lua Plugins easy to add.
-
If you add this plugin to your user plugins - I think it will be a built in plugin on the next version of Gideros (so remove it then). https://www.dropbox.com/s/a4h0zl449mabnnz/virtualpad.zip?dl=0 Basically put the virtualpad folder within the zip…
-
It's supposed to be open sourced into the gideros github. Not sure if that happened though. I can look into making it a 'lua plugin'.
-
You can add extra fonts in a sequence, so the first font is priority then if the character isn't found then it moves to the next. fonts={{file="fonts/main_font.ttf",sizeMult=1.0},{file="fonts/secondary_font.ttf",sizeMult=1.0}} font=TTFont.new(fonts,…
-
Where you are located (users currency and price as a string) + any descriptions you have done in the language of the user. Not sure if the language bit is automatic if you haven't added them manually in the Google play dev panel though.
-
You get the text from the store... iab:addEventListener(Event.PRODUCTS_COMPLETE,function(e) for i = 1, #e.products do local p=e.products[i] --id, title, description and price print(p.productId,p.title,p.description,p.price) end end) iab:req…