Messages

3736

Tutorials / Re: change hotspot for zoomsprite?

« on: 2011-Apr-22 »

Code: (glbasic) [Select]

FUNCTION PaintImage: Name$, x#, y#, alpha#, zoom#, xspot, yspot, yy#
LOCAL h#, w#, img, hh#, ww#, xx#, yy#
x=20
y=20
xspot=1
yspot=1
IF alpha#=0 THEN RETURN
IF Name$=0
// img=GetStr$(Name$, "Sprites") ' Just a name based sprite function rather than number. Not need for test here at all.
ELSE
img=Name$
ENDIF
GETSPRITESIZE img, w, h

// rect maths <- This code math the box where the sprite should been placement
// That one works perfecty as its should. I does this because I might later using scaling#
// (different than zoom, which was FOR resolution scaling).
IF xspot=-1 THEN PX=x#
IF xspot=0 THEN PX=ScreenWidth/2.0-(w#*zoom#/2.0)+x#
IF xspot=1 THEN PX=ScreenWidth-w#*zoom#-x#*zoom#

IF yspot=-1 THEN PY=y#
IF yspot=0 THEN PY=ScreenHeight/2.0-(h*zoom#/2.0)+y#
IF yspot=1 THEN PY=ScreenHeight-h#*zoom#-y#*zoom#
PW=w*zoom#
PH=h*zoom#

// test box using drawrect, where the sprite should been draw directly over.
ALPHAMODE 0.2
DRAWRECT PX, PY, PW, PH, RGB(255, 255, 255)

// some alpha code in that way I prefer. Not a issue in the real alphamode, its just me :-D
IF alpha#>0
alpha#=0-alpha#
ELSE
alpha#=-alpha#
ENDIF
ALPHAMODE alpha#

// draw a sprite top on the drawrect box, but its slighty off. Also some rotation support, not finished, but dont think about it.
SELECT ROTATE
CASE 180
PX=ScreenWidth-PX-PW
PY=ScreenHeight-PY-PH
CASE 0
ZOOMSPRITE img, PX#-((1-zoom#)*w#)/2, PY#-((1-zoom#)*h#)/2, PW#/w#, PH#/h#
DEFAULT
ENDSELECT
ENDFUNCTION

Tried it, seen its works.

Its was somewhere the only one I diddent tried out (1-zoom#). So close :-D.

The only issue is its still sometimes off with one pixel, which should been gone with a real top/left hotspot to avoid that, but elsewise thanks.

3737

Tutorials / change hotspot for zoomsprite?

« on: 2011-Apr-22 »

After trying to math how to math a sprite, based on topleft, center or rightcenter hotsots after about 10-15 hours, then I gave up.

Is is possible to change the hotspot on zoomsprite as well other sprite commands to set on the top left, which would been LOTS easier to math the placement of them? Something a missing command?

Here is the funtion I try to create. The box draw perfect, but zoomsprite is the issue, its not setting on the box as it should:

Code: (glbasic) [Select]

FUNCTION PaintImage: Name$, x#, y#, alpha#, zoom#, xspot, yspot, yy#
zoom#=0.5
x=0
y=0
xspot=1
yspot=-1
IF alpha#=0 THEN RETURN
IF alpha#>0
alpha#=0-alpha#
ELSE
alpha#=-alpha#
ENDIF
LOCAL h#, w#, z#
LOCAL img, hh#, ww#
IF alpha#<>0 THEN ALPHAMODE alpha#
IF Name$=0
img=GetStr$(Name$, "Sprites")
ELSE
img=Name$
ENDIF
GETSPRITESIZE img, w, h

// rect maths
IF xspot=-1 THEN PX=x#
IF xspot=0 THEN PX=ScreenWidth/2.0-(w#*zoom#/2.0)+x#
IF xspot=1 THEN PX=ScreenWidth-w#*zoom#-x#*zoom#

IF yspot=-1 THEN PY=y#
IF yspot=0 THEN PY=ScreenHeight/2.0-(h*zoom#/2.0)+y#
IF yspot=1 THEN PY=ScreenHeight-h#*zoom#-y#*zoom#
PW=w*zoom#
PH=h*zoom#

// ALPHAMODE 0.2
DRAWRECT PX, PY, PW, PH, RGB(255, 255, 255)


SELECT ROTATE
CASE 180
PX=ScreenWidth-PX-PW
PY=ScreenHeight-PY-PH
CASE 0
ZOOMSPRITE img, PX, PY, zoom#, zoom#
DEFAULT
ENDSELECT
ENDFUNCTION

I use this for scaling graphics for any resolutions.

PS. I use name rather than number for ease programmering, so you can coomand the getspr$ out without issue.

PPS. YY# does nothing at all, and is just a placeholder to been removed later.

3738

Bug Reports / Re: Transparent part of sprite causing collision on WebOS 1.4.5

« on: 2011-Apr-21 »

I have to ask:

1. Does this also happens with none transparency png, using pink (etc 8bit png instead of 24bit)?
2. How about using a real alpha png, rather than a transparency color?

Those could been used for col checks only.

3739

GLBasic - en / Re: [ANDROID] First Impressions

« on: 2011-Apr-11 »

Cool. I have planned to wait to App Game Kit, because its validared ot came to Android too, but the language is still not on market. This post cause me to just start on Gl-Basic again, where I planning and starting a new game.

So even I is a die hard iOS user, congratulations, and I hope to see this out too, so I can port it so many mobiles as possible.

Some thing I have to ask:
1. Possible to detect controllers the phone might have, since some phones might have physical controllers (keypad and keyboard)?
2. Touchpad support for Sony Ericsson Xperia Play could been cool, but not required (using the analog joy commands of course). That phone is a very cool Android phone I have seen (My friend have that one).
3. Why not Android v2.1 support. Its have OpenGL and all, so its should been possible to run GlBasic nicely, I guess they threat somewhere like a older iPhone. Android 1.xx is a nogo of course. Howover not important throught.

Something I noticed:
A. Remember there is some bad multitouch screens as well, when you cross 2 fingers in a line, then it goes very bad. Remeber design with that in mind, or possible to disable multitouch (in the game of course).

3740

music/sound / adpcm wav support? (and few other things)

« on: 2011-Apr-11 »

First at all, its common to use compressed format today and have been done that in years. Why does GlBasic still only use PCM-WAV? Its take a lots os hardrive space for a download game, when using many sfx.

for me even ADPCM-Wav format would been much better choice, which is a nice SFX format, even its a pretty old format. Its still a good SFX format, that dont use so much memory as PCM-WAV does.... And for systems, that cant play native that format, could jus uncrompress in load time.

That for is that I have used in years. Ogg would also been nice to been supported for systems that native support it for Music (patent crap), elsewise its should return a error (same with other music formats, like m4a). Howover its not a issue normallt for phones, since carriers allreadt have paid for that (as I aware at).

there is also a missing for a PAUSESOUND() and RESUMESOUND().

Also its would been nice to checkout where the music position is and also to play move the position in the music file, if possible.

I might came with more ideas for better sound commands, since they are really basic right now (but does works, which is important).

3741

GLBasic - en / Re: editor jumps annorying on "no file" on exit.

« on: 2010-Mar-07 »

the code its self works as it should.

This is just do I wanted to automatic load the files with might have varied length of animations.

I now use this:

Code: (glbasic) [Select]

FOR r=1 TO MAXANIMHEADS
FOR i=1 TO 10
t=r*10+i-1
A$="headtile_"+r+"_"+i+".png"
IF DOESFILEEXIST(A$)=1
DEBUG A$+" "+t+"\n"
LOADSPRITE A$, t
ELSE
BREAK
ENDIF
NEXT
NEXT

In the old code, I loaded the sprite regaardless the file was exists or not, then use BREAK when the size of sprite was zero. The code elsewise ran fine, but just jump into the GETSPRITESIZE command (after the LOAD command)after the app exists....

PS. Im are aware of the GENSPRITE(), but is not required in this app.

3742

GLBasic - en / editor jumps annorying on "no file" on exit.

« on: 2010-Mar-07 »

how do I detect if a sprite exists or not, whithout the editor jump to that line on exists... which is pretty annoyring.

I use something like this:

GETSPRITESIZE t, XX, YY

And if XX is 0, I asume there is no sprite here and do some code here.

If a do its on a TRY command, the editor just annoyring jump there instead.

I hate when the editor jump to these commands on exists, so I need to scroll where I was code every time, when I known there is no bug here......

I need to find a with to detect if a sprite exists or not WITHOUT these annoyring jumps.

PS. It might have caused by LOADSPRITE when no file found, but I dont think that is a issue, but using DOESFILEEXIST now instead to avoid that editor jump.

3743

Bug Reports / odd behaiver in ALPHAMODE?

« on: 2010-Mar-06 »

values between 0.0 and 1.0 works as it should, but values between -1.0 and 0 works very odd and can been very confuction to been used the right way.

By now -1 and 0 is the same, but -1 should been blank and not a value close to 0. Its simply seen the command do the other way as its should.

Normally 0 should been the middle point, so 0 is normal, -1 is completly off and 1 is lightest.

This would been much easier to understand.

PS. I known there is a workaround by creating a SETALPHAMODE function and do the math here, but for me its still a bug.