Luke100000 wrote:I don't understand how I can create now a .apk.
I've found this [...] But I don't understand this...
Please no unhelpful comments, thanks.
What part do you not understand?
Have you read the "Building Love for X" on the wiki so you know how to use ndk-build and adb?
Missing Sentinel Software | Twitter FORCIBLY IGNORED.
<leafo> when in doubt delete all of your code
<bartbes> git rm -r *
<bartbes> git commit -m "Fixed all bugs"
<bartbes> git push
The x and y parameters for love.touchmoved (and other touch functions) are the absolute position of the finger on the touch device in normalized [0, 1] coordinates, rather than the change in position since the previous touchmoved event.
tx = 0
ty = 0
mx = 0
my = 0
px = 0
py = 0
gw = love.graphics.getWidth()
gh = love.graphics.getHeight()
function love.draw()
love.graphics.translate(tx, ty)
love.graphics.print(gw.." x ".. gh, 100, 100)
love.graphics.print(mx.." x ".. my, 100, 150)
love.graphics.print(px.." x ".. py, 100, 200)
end
function love.touchpressed(id, x, y, p)
mid = id
mx = x
my = y
px = (gw * (x - mx))
py = (gh * (y - my))
end
function love.touchmoved(id, x, y, p)
if id == mid then
tx = tx + (gw * (x - mx))
ty = ty + (gh * (y - my))
px = (gw * (x - mx))
py = (gh * (y - my))
mx = x
my = y
end
end
function love.keypressed(key)
if key == "escape" then
love.event.quit()
end
end
slime wrote:The x and y parameters for love.touchmoved (and other touch functions) are the absolute position of the finger on the touch device in normalized [0, 1] coordinates, rather than the change in position since the previous touchmoved event.
I think that I added that to the love-android wiki... And made a issue report just to know that it wasn't a bug.
tx = 0
ty = 0
mx = 0
my = 0
px = 0
py = 0
gw = love.graphics.getWidth()
gh = love.graphics.getHeight()
function love.draw()
love.graphics.translate(tx, ty)
love.graphics.print(gw.." x ".. gh, 100, 100)
love.graphics.print(mx.." x ".. my, 100, 150)
love.graphics.print(px.." x ".. py, 100, 200)
end
function love.touchpressed(id, x, y, p)
mid = id
mx = x
my = y
px = (gw * (x - mx))
py = (gh * (y - my))
end
function love.touchmoved(id, x, y, p)
if id == mid then
tx = tx + (gw * (x - mx))
ty = ty + (gh * (y - my))
px = (gw * (x - mx))
py = (gh * (y - my))
mx = x
my = y
end
end
function love.keypressed(key)
if key == "escape" then
love.event.quit()
end
end
Also I really like that script... It's pretty simple
for i, person inipairs(everybody) do [tab]ifnot person.obey then person:setObey(true) end end
love.system.openURL(github.com/pablomayobre)
Hi guys! I have a generic tablet (Tablet Titan 7010) and when I try to run Love for Android it simply displays a blue screen intead of the no-screen.
I've tested it on my phone (Samsung Galaxy Y) and it works perfectly on it. I have no idea why it doesn't work on the tablet. Maybe the GPU drivers don't function properly? But I've had no problem with other games...
I googled around and couldn't fix this issue, I hope you can help me...
Satinxs wrote:Hi guys! I have a generic tablet (Tablet Titan 7010) and when I try to run Love for Android it simply displays a blue screen intead of the no-screen.
I've tested it on my phone (Samsung Galaxy Y) and it works perfectly on it. I have no idea why it doesn't work on the tablet. Maybe the GPU drivers don't function properly? But I've had no problem with other games...
I googled around and couldn't fix this issue, I hope you can help me...
My friend (with a Moto G, android 4.4.2) complains exactly the same thing. The game tested works fine in a Galaxy 2 and Galaxy Tab 2 (10").
Satinxs wrote:Hi guys! I have a generic tablet (Tablet Titan 7010) and when I try to run Love for Android it simply displays a blue screen intead of the no-screen.
I've tested it on my phone (Samsung Galaxy Y) and it works perfectly on it. I have no idea why it doesn't work on the tablet. Maybe the GPU drivers don't function properly? But I've had no problem with other games...
I googled around and couldn't fix this issue, I hope you can help me...
My friend (with a Moto G, android 4.4.2) complains exactly the same thing. The game tested works fine in a Galaxy 2 and Galaxy Tab 2 (10").