sdl4fp-users — For app writers USING the SDL4Freepascal lib.

Re: [Sdl4fp-users] fpc -gh -gc causes invalid read error

[Andreas K. F. <li...@AK...>]

Am Samstag, dem 10. Feb 2007 schrieb James Walter Hofmann:

> pointer $0808BFA0 does not point to valid memory block

When you use -gc the compiler checks, whether a pointer points to a heap
memory block. FPC only knows about the memory, which is allocated by FPC
itself. But that memory is allocated from the libSDL. So FPC doesn't
know anything about it.

You cannot use FPC to check code written in a different language.=20
Use a general debugger for that.

--=20
AKFoerster

[Sdl4fp-users] fpc -gh -gc causes invalid read error

[James W. H. <jho...@uc...>]

With the two above debug options demo02 and demo03 of 
sdl4fpc 1.2.0.0 crash
on FPC 2.0.0/Linux and FPC 2.0.4/Win32:

(these crash reports also used -gl to get a line number)

pointer $0808C0F0 does not point to valid memory block
                                                       No
heap dump by heaptrc unit
Exitcode = 204
Runtime error 204 at $0805E365
   $0805E365
   $08049506  main,  line 95 of demo02.pp

pointer $0808BFA0 does not point to valid memory block
                                                       No
heap dump by heaptrc unit
Exitcode = 204
Runtime error 204 at $0805E95D
   $0805E95D
   $080492AB  RENDER_BALL,  line 95 of demo03.pp
   $080497DF  main,  line 180 of demo03.pp

The culprit in the cases I've looked it is 
SDL_CreateRGBSurface, but there may be more functions 
causing this kind of error. These seem to be "harmless" 
memory errors, since the program works fine - I suspect 
what is being detected as a leak is probably just 
allocations from the C code - but it gets in the way of 
finding errors in my own program. Can it be fixed? I'm 
going to start looking...

Re: [Sdl4fp-users] SDL and GNU Pascal

[Andreas K. F. <li...@AK...>]

----- Forwarded message from "Andreas K. Foerster" <li...@AK...> -----

From: "Andreas K. Foerster" <li...@AK...>
To: gp...@gn...
Subject: Re: SDL and GNU Pascal
Mail-Followup-To: gp...@gn...

Am Mittwoch, dem 01. Nov 2006 schrieb Frank Heckenbach:

> Only CInteger (and its unsigned variants), there's no CLongInt.

Okay, my fault.

> > Note that you have to change "LongInt" to "CInteger" and "PChar"
> > to "CString" in SDL4fp.
> 
> BTW, GPC support both "PChar" and "CString" built-in. However,
> indeed I prefer to write "CString" when I mean a pointer to a "C
> string" (i.e., Chr(0)-terminated array of chars), instead of a
> pointer to a single character (which "PChar" is according to a
> common way of notation).

I knew that there is PChar in GPC, but I also prefer CString because of
it's name.

> One way to avoid the ifdefs might be a macro that expands to
> "external 'SDL'" in FPC, and just "external" in GPC (and perhaps
> taking care of the "cdecl" as well for FPC,

That's a very good idea.
I've done it this way now:

{$IfDef __GPC__}
  {$L SDL}
  {$DEFINE libSDL external name}
{$EndIf}

{$IfDef FPC}
  {$MACRO ON}
  {$DEFINE libSDL:=cdecl; external 'SDL' name}
{$EndIf}

[...]

function SDL_Init(flags: Uint32): CInteger; libSDL 'SDL_Init';

> to further save typing).

It's not for the typing, but the result is much more readable.

> > C is case sensitive, while Pascal is not. So in GPC all Pascal identifiers
> > are converted to lowercase at an early stage, this includes the
> > procedure names. So you have a problem when your C identifiers need
> > uppercase letters. This can only be solved by using an attribute which
> > mentions the name again with its capitalisation: "name 'Example'".
> 
> Even when they don't need any uppercase letters, it's recommended to
> always specify the linker name for external declarations.

I see that there are reasons for the compiler developers.
But it is much more convenient for the programmer, if the name
would simply be deduced from the Pascal name with its capitalisation, 
as it is in Free Pascal.

> > Well I still have a problem with CString parameters. FPC needs a type
> > cast, while GPC doesn't accept a type cast here. I "solved" it again
> > with "IfDef"s. Does anybody know a better solution?
> 
> Perhaps another macro (just a quick idea, as I actually don't like
> macros too much), that does a type-cast in FPC and nothing in GPC.
> (Perhaps it could even be a type equal to CString in FPC, though
> with another name, working as a type-cast by itself, and a nop-macro
> in GPC.)

Can you tell me more about "nop-macros" in GPC?

Another macro would even be dirtier than the ifdef.
Fortunately there are just few (only one?) situation, where that's
needed in the SDL - so that doesn't harm much in my program.

-- 
AKFoerster

----- End forwarded message -----

-- 
AKFoerster

[Sdl4fp-users] SDL and GNU Pascal

[Andreas K. F. <li...@AK...>]

Hello sdl4fp-users,

As some of you might remember, I wanted to use the SDL also with GNU=20
Pascal in my project AKFQuiz. I tried to fiddle with the source code=20
of SDL4Freepascal. But there was too much code to change just to find
out how it works...

So I decided to leave SDL4fp away and implement the few things I need=20
=66rom scratch.

My project now is fully functional with GPC and SDL. It is not yet in
the released version, but you can check out the CVS as described on the
homepage (see link at the end of this mail).

Now I want to share my findings with you, so probably you can use it for
SDL4Freepascal...


First of all, the types for variables are very different. SDL4fp uses
"LongInt" for what is "int" in C - because LongInt happens to be 32Bit
wide in FPC. But in GPC a LongInt is "at least" :-) 64bit wide! So it=20
doesn't fit.=20

Older versions of GPC intentionally kept the variable types compatible=20
to their counterparts in C. Newer versions broke with that and introduced
speacial types, like CInteger or CLongInt.

Another difference to FPC is, that in GPC you have a more fine grained=20
access to determine attributes, so you have really control about the=20
size of variables.

Here is the code snipplet for the types (from my "qsys.pas"):

-----------------------------------------------------------------------
{$IfDef __GPC__}

  type=20
    Uint8  =3D Cardinal attribute (Size =3D  8);
    Uint16 =3D Cardinal attribute (Size =3D 16);
    Sint16 =3D Integer  attribute (Size =3D 16);
    Uint32 =3D Cardinal attribute (Size =3D 32);
    Sint32 =3D Integer  attribute (Size =3D 32);
    pByte  =3D ^Uint8;
 =20
  {$if __GPC_RELEASE__ < 20041218}
    type CInteger =3D Integer;
  {$EndIf} { __GPC_RELEASE__ }
 =20
{$Else} { not __GPC__ }

  type=20
    CInteger =3D LongInt; { @@@ for 32-Bit systems }
    CString  =3D PChar;
    Uint8    =3D byte;
    Uint16   =3D word;
    Sint16   =3D SmallInt;
    Uint32   =3D cardinal;
    Sint32   =3D LongInt;
    pByte    =3D ^Uint8;

{$EndIf} { not __GPC__ }
-----------------------------------------------------------------------

Note that you have to change "LongInt" to "CInteger" and "PChar"
to "CString" in SDL4fp.

SDL4fp links to the library by using the name 'SDL' after the "external"
modifier. This doesn't work in GPC (yet). In GPC you have to use the
compiler directive "{$L SDL}".=20
In FPC there's also a possability to use it in a similar way with
"{$LinkLib SDL}"... well it works, but not in every situation. So I
decided to keep the name after the external clause, but with "IfDef"s
around it. GPC compiles it without the IfDef, but there are lot of
warning messages then.

In FPC you must use the modifier "cdecl". In GPC that is the default,
so you don't need it there. You can however declare it with
"attribute(cdecl)", so you can simply write a macro to modify the "cdecl":
"{$Define cdecl attribute(cdecl)}".

C is case sensitive, while Pascal is not. So in GPC all Pascal identifiers
are converted to lowercase at an early stage, this includes the
procedure names. So you have a problem when your C identifiers need
uppercase letters. This can only be solved by using an attribute which
mentions the name again with its capitalisation: "name 'Example'". This
name isn't converted to lower case, since it's a string-constant.
FPC doesn't need that, but it doesn't harm there either.

putting everything together it looks like in this example:

  procedure SDL_WM_SetCaption(title, icon: CString); cdecl;
              external {$IfDef FPC}'SDL'{$EndIf} name 'SDL_WM_SetCaption';

Well I still have a problem with CString parameters. FPC needs a type
cast, while GPC doesn't accept a type cast here. I "solved" it again
with "IfDef"s. Does anybody know a better solution?


Please have a look at my source code for more information:
http://cvs.sv.nongnu.org/viewcvs/akfquiz/srcbin/?root=3Dakfquiz
The relevant units are "sdlgrph.pas" and "sdlsnd.pas".=20
The type definitions are in "qsys.pas".

If you use my findings in SDL4fp, it would be nice, if you would mention=20
me there as "AKFoerster".


Related Links:

GNU Pascal:      http://www.gnu-pascal.de/
Free Pascal:     http://www.freepascal.org/
SDL:             http://www.libsdl.org/
SDL4Freepascal:  http://sdl4fp.sourceforge.net/
AKFQuiz:         http://akfquiz.nongnu.org/

--=20
AKFoerster

[Sdl4fp-users] SDL_ColorArray

[Andreas K. F. <li...@AK...>]

Hello,

I just had to use the function SDL_SetColors. The second parameter is of
the type SDL_ColorArray. That is defined as
SDL_ColorArray = Array[0..0] of SDL_Color

An array with just one possible element? Does that make sense?

I tried to make my own Array and then typecast it to SDL_ColorArray, but
that doesn't work. Now I set the colors one by one. But I think the type
SDL_Color would have done the same job.

Isn't SDL_ColorArray internally the same as SDL_Color? I think the type
PSDL_Color would fit there much better.

-- 
AKFoerster

Re: [Sdl4fp-users] Problem using font surface

[Matthias <ma...@gm...>]

Hi there,

Couldn't find a demo file which uses the commadn TTF_RENDERTEXT_BLENDED? I 
have downloaded the additional files demo04.pp and demo05.pp but they didn't 
contain this commnd as well. Which demo you refer to?

(Btw I added SDL_EnableKeyRepeat to events.pp, Elio or you interessted?)

Greets,

Matthias

----- Original Message ----- 
From: "Daniel F Moisset" <dmo...@ar...>
To: <sdl...@li...>
Sent: Monday, May 01, 2006 6:08 PM
Subject: Re: [Sdl4fp-users] Problem using font surface


> On Mon, 2006-05-01 at 14:45 +0200, Matthias wrote:
>> Thanks for your reply. So I will avoid using TTF_RENDERTEXT_BLENDED...
>>
>> There a further question came up here. Well, if I use 
>> TTF_RENDERTEXT_SOLID
>> to create a wurface with some text and blit it afterwards to the display
>> surface, the colorkey seems to be set automatically. Is this true?
>>
>
> SDL4FP includes a demo using blneded text. Does it work for you?
>
> Regards,
>
> Daniel
>
> -- 
> "Why program by hand in five days what you can spend five years of your
> life automating."
>            -- Terrence Parr, ANTLR author
>
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Sdl4fp-users mailing list
> Sdl...@li...
> https://lists.sourceforge.net/lists/listinfo/sdl4fp-users
> 

Re: [Sdl4fp-users] Problem using font surface

[Daniel F M. <dmo...@ar...>]

On Mon, 2006-05-01 at 14:45 +0200, Matthias wrote:
> Thanks for your reply. So I will avoid using TTF_RENDERTEXT_BLENDED...
> 
> There a further question came up here. Well, if I use TTF_RENDERTEXT_SOLID 
> to create a wurface with some text and blit it afterwards to the display 
> surface, the colorkey seems to be set automatically. Is this true?
> 

SDL4FP includes a demo using blneded text. Does it work for you?

Regards,

	Daniel

-- 
"Why program by hand in five days what you can spend five years of your
life automating."
            -- Terrence Parr, ANTLR author

Re: [Sdl4fp-users] runtime error on alloc to pSDL_RECT

[Matthias <ma...@gm...>]

Thanks.

I think before I worked on errors (forgotten allocation or wrong array 
length and so on) at other location in the progam code. So this could truely 
be the explanation.

Greets,
Matthias
----- Original Message ----- 
From: "Daniel F Moisset" <dmo...@ar...>
To: <sdl...@li...>
Sent: Sunday, April 30, 2006 11:37 PM
Subject: Re: [Sdl4fp-users] runtime error on alloc to pSDL_RECT


> On Fri, 2006-04-28 at 22:34 +0200, Matthias wrote:
>> Hi there.
>>
>> When trying to compile I got runtime error 216 at allocation of
>> memory. While in debug mode I receive the messege you see in the
>> picture.
>>
>> http://unterhaltung.freepage.de/tycoon/sam/sdlerr.GIF
>>
>> The curious thing is, this allocation didn't make any problems before.
>> Any suggestions what is going wrong here?
>
> An usual cause of allocation failures is corrupt data structures in the
> heap. Probably you are accessing a pointer after freeing it, or
> accessing a dynamic array out of its bounds.
>
> These kind of errors disappear and reappear randomly, because they may
> depend on previous contents of the memory. I can't be 100% sure, but I
> bet your problem is this and not one related to the SDL library (anyway,
> you are just using a record allocation there, not a library function).
>
> Regards,
> Daniel
>
>
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Sdl4fp-users mailing list
> Sdl...@li...
> https://lists.sourceforge.net/lists/listinfo/sdl4fp-users
> 

Re: [Sdl4fp-users] Problem using font surface

[Matthias <ma...@gm...>]

Thanks for your reply. So I will avoid using TTF_RENDERTEXT_BLENDED...

There a further question came up here. Well, if I use TTF_RENDERTEXT_SOLID 
to create a wurface with some text and blit it afterwards to the display 
surface, the colorkey seems to be set automatically. Is this true?

Greets,
Matthias
----- Original Message ----- 
From: "Christian Speckner" <csp...@fr...>
To: <sdl...@li...>
Sent: Sunday, April 30, 2006 7:40 PM
Subject: Re: [Sdl4fp-users] Problem using font surface


> Oops, sorry, I just saw that you already use SDL_DisplayFormat; this 
> really
> looks like a driver problem.
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Sdl4fp-users mailing list
> Sdl...@li...
> https://lists.sourceforge.net/lists/listinfo/sdl4fp-users
> 

Re: [Sdl4fp-users] runtime error on alloc to pSDL_RECT

[Daniel F M. <dmo...@ar...>]

On Fri, 2006-04-28 at 22:34 +0200, Matthias wrote:
> Hi there. 
>  
> When trying to compile I got runtime error 216 at allocation of
> memory. While in debug mode I receive the messege you see in the
> picture. 
>  
> http://unterhaltung.freepage.de/tycoon/sam/sdlerr.GIF
>  
> The curious thing is, this allocation didn't make any problems before.
> Any suggestions what is going wrong here?

An usual cause of allocation failures is corrupt data structures in the
heap. Probably you are accessing a pointer after freeing it, or
accessing a dynamic array out of its bounds.

These kind of errors disappear and reappear randomly, because they may
depend on previous contents of the memory. I can't be 100% sure, but I
bet your problem is this and not one related to the SDL library (anyway,
you are just using a record allocation there, not a library function).

Regards,
	Daniel

Re: [Sdl4fp-users] Problem using font surface

[Christian S. <csp...@fr...>]

Oops, sorry, I just saw that you already use SDL_DisplayFormat; this really 
looks like a driver problem.

Re: [Sdl4fp-users] Problem using font surface

[Christian S. <csp...@fr...>]

AFAIK, blitting between surfaces with different pixel formats should work 
without any problems (slow though due to the neccesary conversions). Since 
SDL tries to use hardware acceleration when possible, the error might be 
located on the OS side - you might try to update your video drivers.
Anyway, there exists a SDL function which converts surfaces to display format

function SDL_DisplayFormat(source: PSDL_Surface): PSDL_Surface;

Am Samstag, 29. April 2006 18:18 schrieb Matthias:
> Hi there.
>
> Problem is related to TTF unit.
>
> {code}
> temporary_text_surface:=TTF_BRENDERTEXT_BLENDED(...);
> converted_text_surface:=SDL_DISPLAYFORMAT(temporary_text_surface);
> {end code}
>
> If I blit temporary_text_surface to display surface all works well. If I
> try to blit converted_text_surface I get this:
>
> http://unterhaltung.freepage.de/tycoon/sam/sdlerr2.GIF
> (here you see two different tries to blit a converted text)
>
> If I use TTF_RENDERTEXT_SOLID this problem does not occur. This maybe has
> something to do with the fact that the last command creates an
> 8-bit-surface while TTF_RENDERTEXT_BLENDED creates a 32-bit one?
>
> How to ensure the text surface has the same format as the display surface?
>
> Thanks alot.
>
> Greets,
> Matthias

[Sdl4fp-users] Problem using font surface

[Matthias <ma...@gm...>]

Hi there.

Problem is related to TTF unit.

{code}
temporary_text_surface:=3DTTF_BRENDERTEXT_BLENDED(...);
converted_text_surface:=3DSDL_DISPLAYFORMAT(temporary_text_surface);
{end code}

If I blit temporary_text_surface to display surface all works well. If I =
try to blit converted_text_surface I get this:

http://unterhaltung.freepage.de/tycoon/sam/sdlerr2.GIF
(here you see two different tries to blit a converted text)

If I use TTF_RENDERTEXT_SOLID this problem does not occur. This maybe =
has something to do with the fact that the last command creates an =
8-bit-surface while TTF_RENDERTEXT_BLENDED creates a 32-bit one?

How to ensure the text surface has the same format as the display =
surface?

Thanks alot.

Greets,
Matthias

[Sdl4fp-users] RE: runtime error on alloc to pSDL_RECT

[Matthias <ma...@gm...>]

Hi there.

I just used the readln to check where the error occurs. I could have =
removed them and the error would occur nevertheless. It has something to =
do with the allocation of the memory.=20

Problem solved though. Anyhow I didn't change the code (just slept one =
night) and today suddenly the error does not occur anymore..... My =
explanation: Shut down and restart computer has flashed RAM.

Thanks so far,

Matthias
  ----- Original Message -----=20
  From: Samuel Lid=E9n Borell=20
  To: sdl...@li...=20
  Sent: Saturday, April 29, 2006 11:40 AM
  Subject: Re: [Sdl4fp-users] RE: runtime error on alloc to pSDL_RECT


  Hi,

  ReadLn should work without any variable parameter. It shouldn't crash.

  /Samuel

  julian ganz wrote:=20

i'm not compeately shure weather this is the fault that causes the =
error, but  the procedure "readln" normaly needs a var where it can put =
the data.
( you could define a dummy and use it as parameter "readln( dummy )" )
but it also could be any problem with the "sdl-code" itself or another =
thing.
did you (re-)installed any libary or the compiler itself? could it be =
that it doesn't load the units in your standart unit dir? ( i had this =
problem when i reinstalled my system )

the procedure readln may use pointer-based adressing of input data, so =
when there is no var, it tries to give the data to any adress. because =
of this you get runtime error 216 ( "general frotection fault" )

hope i could help you
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=3D021192



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, =
security?
Get stuff done quickly with pre-integrated technology to make your job =
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache =
Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121642
_______________________________________________
Sdl4fp-users mailing list
Sdl...@li...
https://lists.sourceforge.net/lists/listinfo/sdl4fp-users

  

Re: [Sdl4fp-users] RE: runtime error on alloc to pSDL_RECT

[<sam...@br...>]

Hi,

ReadLn should work without any variable parameter. It shouldn't crash.

/Samuel

julian ganz wrote:

>
>i'm not compeately shure weather this is the fault that causes the error, but  the procedure "readln" normaly needs a var where it can put the data.
>( you could define a dummy and use it as parameter "readln( dummy )" )
>but it also could be any problem with the "sdl-code" itself or another thing.
>did you (re-)installed any libary or the compiler itself? could it be that it doesn't load the units in your standart unit dir? ( i had this problem when i reinstalled my system )
>
>the procedure readln may use pointer-based adressing of input data, so when there is no var, it tries to give the data to any adress. because of this you get runtime error 216 ( "general frotection fault" )
>
>hope i could help you
>_______________________________________________________________
>SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
>kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
>
>
>
>-------------------------------------------------------
>Using Tomcat but need to do more? Need to support web services, security?
>Get stuff done quickly with pre-integrated technology to make your job easier
>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>_______________________________________________
>Sdl4fp-users mailing list
>Sdl...@li...
>https://lists.sourceforge.net/lists/listinfo/sdl4fp-users
>
>  
>

[Sdl4fp-users] RE: runtime error on alloc to pSDL_RECT

[julian g. <shi...@we...>]

>Hi there.
>
>When trying to compile I got runtime error 216 at allocation of memory.
>While in debug mode I receive the messege you see in the picture.
>
>http://unterhaltung.freepage.de/tycoon/sam/sdlerr.GIF
>
>The curious thing is, this allocation didn't make any problems before.
>Any suggestions what is going wrong here?
>
>Greets,
>Matthias

i'm not compeately shure weather this is the fault that causes the error, but  the procedure "readln" normaly needs a var where it can put the data.
( you could define a dummy and use it as parameter "readln( dummy )" )
but it also could be any problem with the "sdl-code" itself or another thing.
did you (re-)installed any libary or the compiler itself? could it be that it doesn't load the units in your standart unit dir? ( i had this problem when i reinstalled my system )

the procedure readln may use pointer-based adressing of input data, so when there is no var, it tries to give the data to any adress. because of this you get runtime error 216 ( "general frotection fault" )

hope i could help you
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192

Re: [Sdl4fp-users] Converting images (SDL_DISPLAYFORMAT)

[Daniel F M. <dmo...@ar...>]

On Mon, 2006-03-27 at 03:22 +0200, Matthias wrote:
> Hi there,
>  
> got a problem.
>  
> I load a common 24 bit bitmap graphic file to an image (SDL_LOADBMP)
> then the surface should have surface^.format.bitsperpixel of 24 but
> instead I got 32, why?

The BMP loader sometimes align every pixel to doublewords (converting 24
to 32 bits). You don't have more colors and it's more expensive in
memory, but operations are faster for 32 bit pixels instead of 24.

	Daniel

-- 
"Why program by hand in five days what you can spend five years of your
life automating."
            -- Terrence Parr, ANTLR author

[Sdl4fp-users] runtime error on alloc to pSDL_RECT

[Matthias <ma...@gm...>]

Hi there.=20

When trying to compile I got runtime error 216 at allocation of memory. =
While in debug mode I receive the messege you see in the picture.=20

http://unterhaltung.freepage.de/tycoon/sam/sdlerr.GIF

The curious thing is, this allocation didn't make any problems before. =
Any suggestions what is going wrong here?

Greets,
Matthias

Re: [Sdl4fp-users] When i run examples demos at windows i can't move the window where the example is running!

[Elio C. <el...@mi...>]

El Mar 25 Abr 2006 18:04, alberto salazar escribi=F3:
> I'm sorry, mi english is very bad. What i need to do exactly?. Thanx.

Lo que Matthias dice es que si no est=E1s usando el video, la ventana se va=
 a=20
borrar ya que esta no recuerda que es lo que tiene dibujado. Ya cuando haga=
s=20
una aplicaci=F3n/juego real esto no debe causar problemas, ya que usualment=
e=20
est=E1s actualizando la pantalla todo el tiempo, as=ED que aun que se borre=
 una=20
parte, esta es prontamente repintada.

En otras palabras, no te preocupes mucho por este problema.

>
>   Alberto.
>
> 2006/4/25, Matthias <ma...@gm...>:
> > I know this behaviour. I think this just happens if you don't use the
> > video window. As soon as you go on developing your program and the scre=
en
> > output is used extensivly the screen will never get white/break up
> > anymore.
> >
> > Matthias
> >
> > ----- Original Message -----
> > *From:* alberto salazar <cap...@gm...>
> > *To:* sdl...@li...
> > *Sent:* Monday, April 24, 2006 1:41 PM
> > *Subject:* [Sdl4fp-users] When i run examples demos at windows i can't
> > move the window where the example is running!
> >
> >
> >  Hi,
> >
> >  That's my problem. When i move the window then the example stop and sh=
ow
> > white color.
> >
> >  Now in spanish:
> >
> >  Hola,
> >
> >  Mi problema es que compilando los ejemplos de la SDL en Windows no pue=
do
> > mover la ventana en la que se ejecutan, porque
> >  si lo hago la ventana se pone en color blanco... Por cierto enhorabuena
> > t=EDo por el port!. Un saludo!,
> >
> >  Alberto.

Re: [Sdl4fp-users] When i run examples demos at windows i can't move the window where the example is running!

[Daniel F M. <dmo...@ar...>]

On Mon, 2006-04-24 at 13:41 +0200, alberto salazar wrote:
>  
>  Hi,
>  
>  That's my problem. When i move the window then the example stop and
> show white color.

Could you describe your problem in more detail? All the window becomes
blank? part of it? only the part that goes outside the screen/below
other windows? All the demos have the same problem?

Regards,
	Daniel

-- 
"Why program by hand in five days what you can spend five years of your
life automating."
            -- Terrence Parr, ANTLR author

Re: [Sdl4fp-users] When i run examples demos at windows i can't move the window where the example is running!

[alberto s. <cap...@gm...>]

I'm sorry, mi english is very bad. What i need to do exactly?. Thanx.

  Alberto.

2006/4/25, Matthias <ma...@gm...>:
>
> I know this behaviour. I think this just happens if you don't use the
> video window. As soon as you go on developing your program and the screen
> output is used extensivly the screen will never get white/break up anymor=
e.
>
> Matthias
>
> ----- Original Message -----
> *From:* alberto salazar <cap...@gm...>
> *To:* sdl...@li...
> *Sent:* Monday, April 24, 2006 1:41 PM
> *Subject:* [Sdl4fp-users] When i run examples demos at windows i can't
> move the window where the example is running!
>
>
>  Hi,
>
>  That's my problem. When i move the window then the example stop and show
> white color.
>
>  Now in spanish:
>
>  Hola,
>
>  Mi problema es que compilando los ejemplos de la SDL en Windows no puedo
> mover la ventana en la que se ejecutan, porque
>  si lo hago la ventana se pone en color blanco... Por cierto enhorabuena
> t=EDo por el port!. Un saludo!,
>
>  Alberto.
>
>

Re: [Sdl4fp-users] When i run examples demos at windows i can't move the window where the example is running!

[Matthias <ma...@gm...>]

I know this behaviour. I think this just happens if you don't use the =
video window. As soon as you go on developing your program and the =
screen output is used extensivly the screen will never get white/break =
up anymore.

Matthias
  ----- Original Message -----=20
  From: alberto salazar=20
  To: sdl...@li...=20
  Sent: Monday, April 24, 2006 1:41 PM
  Subject: [Sdl4fp-users] When i run examples demos at windows i can't =
move the window where the example is running!



   Hi,

   That's my problem. When i move the window then the example stop and =
show white color.

   Now in spanish:

   Hola,

   Mi problema es que compilando los ejemplos de la SDL en Windows no =
puedo mover la ventana en la que se ejecutan, porque=20
   si lo hago la ventana se pone en color blanco... Por cierto =
enhorabuena t=EDo por el port!. Un saludo!,

   Alberto.

[Sdl4fp-users] When i run examples demos at windows i can't move the window where the example is running!

[alberto s. <cap...@gm...>]

 Hi,

 That's my problem. When i move the window then the example stop and show
white color.

 Now in spanish:

 Hola,

 Mi problema es que compilando los ejemplos de la SDL en Windows no puedo
mover la ventana en la que se ejecutan, porque
 si lo hago la ventana se pone en color blanco... Por cierto enhorabuena t=
=EDo
por el port!. Un saludo!,

 Alberto.

Re: [Sdl4fp-users] blitting outside screen area

[Matthias <ma...@gm...>]

Not too easy, because the whole process of sprite management is done by 
objects. But you helped me alot already. I tried the same thing with another 
sprite and then the parts blitted outside didn't get cut (don't know why I 
didn't try before; probably because I didn't know what to expect).

So, now I know it should have something to do with my code. If I figured out 
what exactly is causing this and it might be interesting for you I will post 
it. If it is caused by something like "oh damn, forgot to NEW the 
pointer..." I won't post.

So thanks alot Elio!

Greets,
Matthias


----- Original Message ----- 
From: "Elio Cuevas Gómez" <el...@mi...>
To: <sdl...@li...>
Sent: Sunday, April 23, 2006 2:09 AM
Subject: Re: [Sdl4fp-users] blitting outside screen area


Not sure why is this happening... Could you provide us with a code sample? I
have never seen this behavior before.

El Sáb 22 Abr 2006 10:49, Matthias escribió:
> Hi there.
>
> I have strange behaviour if I blit outside screen area. I used
> SDL_SETCLIPRECT to define the clipping area (the error described next
> occurs if I don't define clip area, too). The clip area is exactly the
> screen area (it returns TRUE).
>
> I noticed that if I clipped an image outside the area and later try to 
> blit
> it to the visible area the image won't be seen.
>
> Next I tried to clip an image (200 x 200) at a position (for example x=
> 200, y= -100) so it would be partially in visible area and other part
> outside screen area. Then, as expected, the partial part inside screen 
> area
> is shown. - But if I try to clip it to another part of the screen, so the
> whole image should be seen, only the partial part is seen.
>
> Most curious thing about this: I blitted the image, after the clipping 
> half
> outside the screen as described before, at position (0,0)... instead of an
> [200 x 200]-Image with the first part (200 x 100) cleared I just got the
> shown part at (0,0) so it seems as if the image got cut or shrinked by
> half. But if I check the value of width and height of image it stayed 200 
> x
> 200. I am really not sure how to explain this.
>
> Any hints how to let images be blitable after blitting them to outside
> area? What is the reason why it does not work as described?
>
> Thanks a lot!
>
> Greets,
> Matthias


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job 
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=k&kid0709&bid&3057&dat1642
_______________________________________________
Sdl4fp-users mailing list
Sdl...@li...
https://lists.sourceforge.net/lists/listinfo/sdl4fp-users

Re: [Sdl4fp-users] blitting outside screen area

[Elio C. <el...@mi...>]

Not sure why is this happening... Could you provide us with a code sample? =
I=20
have never seen this behavior before.

El S=E1b 22 Abr 2006 10:49, Matthias escribi=F3:
> Hi there.
>
> I have strange behaviour if I blit outside screen area. I used
> SDL_SETCLIPRECT to define the clipping area (the error described next
> occurs if I don't define clip area, too). The clip area is exactly the
> screen area (it returns TRUE).
>
> I noticed that if I clipped an image outside the area and later try to bl=
it
> it to the visible area the image won't be seen.
>
> Next I tried to clip an image (200 x 200) at a position (for example x=3D
> 200, y=3D -100) so it would be partially in visible area and other part
> outside screen area. Then, as expected, the partial part inside screen ar=
ea
> is shown. - But if I try to clip it to another part of the screen, so the
> whole image should be seen, only the partial part is seen.
>
> Most curious thing about this: I blitted the image, after the clipping ha=
lf
> outside the screen as described before, at position (0,0)... instead of an
> [200 x 200]-Image with the first part (200 x 100) cleared I just got the
> shown part at (0,0) so it seems as if the image got cut or shrinked by
> half. But if I check the value of width and height of image it stayed 200=
 x
> 200. I am really not sure how to explain this.
>
> Any hints how to let images be blitable after blitting them to outside
> area? What is the reason why it does not work as described?
>
> Thanks a lot!
>
> Greets,
> Matthias