I am working on a wince game and want to do some fadein/out works on a vga
screen.
I use alphablt in IDirectDrawSurface, but it only support a constant 50%
alpha.
When I blt a 320x240 image on a 480x640 screen, alphablt give me about 12
fps plus filling a backbuffer black , blt another 320x240
On Tue, 20 Oct 2009 17:14:33 +0200, Jonas Maebe
wrote:
> On 20 Oct 2009, at 16:43, Matthias Klumpp wrote:
>
>> Linking build/project1
>> /usr/bin/ld: warning: bin/link.res contains output sections; did you
>> forget
>> -T?
>> ./libipkinject.so: undefined reference to `fpc_geteipasebx'
>> projec
On 20 Oct 2009, at 16:43, Matthias Klumpp wrote:
Linking build/project1
/usr/bin/ld: warning: bin/link.res contains output sections; did you
forget
-T?
./libipkinject.so: undefined reference to `fpc_geteipasebx'
project1.lpr(42,1) Error: Error while linking
Do you have any idea why this hap
Hello!
I use FPC 2.3.1 to let FPC compile shared libraries with PIC code. (PIC
support is broken in FPC 2.2.4)
My shared lib compiles successful, but if I compile a project which uses
this library, I get this:
Linking build/project1
/usr/bin/ld: warning: bin/link.res contains output sections; did
On 20/10/2009, Michael Van Canneyt wrote:
> Only the relative order of y,m,d is needed from shortdateformat.
> So the actual number, 1,2 or 4 ys is not relevant. You are still thinking
> that it uses the actual dateformat, when it does not.
Ah, I get it now! Sorry, I'm was a bit slow there. :
On 20/10/2009, Michael Van Canneyt wrote:
>
> It is mentioned in topic 'Date and time formatting characters' of the FPC
> docs.
I blame my mistake on the broken IPF output generated from 'fpdoc'. My
new INF help viewer, 'docview', did not find any help on "formatting
characters", so I thought i
On Mon, Oct 19, 2009 at 11:20:50PM +0100, Frank Peelo wrote:
> Gustavo Enrique Jimenez wrote:
>> 2009/10/18 Tom Verhoeff :
>>> A simple example is the situation where one needs to calculate
>>> the replacement resistor value R for parallel resistors having
>>> values R1, R2, ..., Rk. The formula i
On Mon, Oct 19, 2009 at 02:57:10PM -0300, Gustavo Enrique Jimenez wrote:
> 2009/10/18 Tom Verhoeff :
> > A simple example is the situation where one needs to calculate
> > the replacement resistor value R for parallel resistors having
> > values R1, R2, ..., Rk. The formula is R = 1/(1/R1 + 1/R2 +
On Tue, 20 Oct 2009, Graeme Geldenhuys wrote:
On 20/10/2009, Graeme Geldenhuys wrote:
PS:
Oh and a nice hidden little features (I couldn't find documentation
for). When you specify a date format as '/mm/dd' or dd/mm/yy
etc... The '/' character is NOT the separator!
Correction, tha
On Tue, 20 Oct 2009, Graeme Geldenhuys wrote:
On 20/10/2009, Michael Van Canneyt wrote:
-
Call StrToDate to parse a string that specifies a date. If S does
[...]
First lines say it all. "dd/mm/yyy hh:nn" is not supposed t
On 20/10/2009, Graeme Geldenhuys wrote:
> PS:
> Oh and a nice hidden little features (I couldn't find documentation
> for). When you specify a date format as '/mm/dd' or dd/mm/yy
> etc... The '/' character is NOT the separator!
Correction, that applies to FormateDateTime(), not StrToDate
On 20/10/2009, Michael Van Canneyt wrote:
>
> The error is correct, since 05/05/1999 is not a valid date.
> It should use - instead of / . I've adapted the example.
But couldn't you simply have forced DateSeparator to "-".
Also could we try not to have such an obscure example - using day and
On 20/10/2009, Michael Van Canneyt wrote:
> -
> Call StrToDate to parse a string that specifies a date. If S does
[...]
> First lines say it all. "dd/mm/yyy hh:nn" is not supposed to work.
That's up for discussion! :-) It says t
On Tue, 20 Oct 2009, Graeme Geldenhuys wrote:
On 20/10/2009, Michael Van Canneyt wrote:
It is documented:
and the documented example "ex19.pp" causes the same error!
--
$ cp /opt/fpcdocs_svn/sysutex/ex19.pp ex19.pas
$ fpc ex19.pas
Free Pascal Compiler version 2.3
On Tue, 20 Oct 2009, Graeme Geldenhuys wrote:
On 20/10/2009, Michael Van Canneyt wrote:
Strip the time part.
You are feeding a date/time pair to something that expects ONLY a date.
Surely it must be able to handle that? Delphi does. Extract what it
needs and leave/ignore the rest?
On 20/10/2009, Michael Van Canneyt wrote:
>
> Strip the time part.
>
> You are feeding a date/time pair to something that expects ONLY a date.
Surely it must be able to handle that? Delphi does. Extract what it
needs and leave/ignore the rest?
--
Regards,
- Graeme -
On 20/10/2009, Michael Van Canneyt wrote:
>
> It is documented:
and the documented example "ex19.pp" causes the same error!
--
$ cp /opt/fpcdocs_svn/sysutex/ex19.pp ex19.pas
$ fpc ex19.pas
Free Pascal Compiler version 2.3.1 [2009/10/08] for x86_64
Copyright (c) 1993-2009
On Tue, 20 Oct 2009, Graeme Geldenhuys wrote:
On 20/10/2009, Michael Van Canneyt >
1. StrToDate uses shortdateformat.
2. StrToDate DOES NOT use shortdateformat to check the actual format;
because it accepts only dates of the form N1/N2/N3
- it uses ShortDateFormat ONLY to determine
On Tue, 20 Oct 2009, Graeme Geldenhuys wrote:
On 20/10/2009, Michael Van Canneyt wrote:
You make a common assumption, which is mistaken:
StrToDate(DateToStr(date)) generally does not work.
Crap! And that is pretty much what the tiOPF unit test is testing for.
So why is StrToDate() so
On 20/10/2009, Michael Van Canneyt >
> 1. StrToDate uses shortdateformat.
>
> 2. StrToDate DOES NOT use shortdateformat to check the actual format;
>because it accepts only dates of the form N1/N2/N3
>- it uses ShortDateFormat ONLY to determine the order of y,m,d
>- it uses DateSepar
On 20/10/2009, Michael Van Canneyt wrote:
>
> You make a common assumption, which is mistaken:
> StrToDate(DateToStr(date)) generally does not work.
Crap! And that is pretty much what the tiOPF unit test is testing for.
So why is StrToDate() so different to Delphi? In Delphi, the above
mentio
Jonas,
> In theory this is of course possible, but in practice this is extremely
> error prone due to the nature of signal handlers. Furthermore, adding extra
> global variables to the interface of the system unit is very much frowned
> upon, and this would be required since the signal handling ha
On Tue, 20 Oct 2009, Graeme Geldenhuys wrote:
Compiling the project works fine under FPC 2.3.1 (linux 64bit), but
running it, i get a EConvertError and I don't know why.
I am telling sysutils what LongDateFormat is like, but it still fails.
Any ideas?
It is documented:
1. StrToDate uses sh
Compiling the project works fine under FPC 2.3.1 (linux 64bit), but
running it, i get a EConvertError and I don't know why.
I am telling sysutils what LongDateFormat is like, but it still fails.
Any ideas?
---
program project1;
{$mode objfpc}{$H+}
uses
{$IFDEF UNIX}{$IFDE
On 20 Oct 2009, at 10:45, fpcl...@silvermono.co.za wrote:
Have you considered implementing the foreach construct similar to
that found
in many modern languages?
You may want to subscribe to the fpc-devel list, as a discussion on
this topic was just started there.
To everyone: please kee
Hi Guys,
Have you considered implementing the foreach construct similar to that found
in many modern languages?
Regards,
Nino
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
> 2009/10/20 :
> > The comment on line 54 should perhaps be reworded to reflect that
> > although it's not implemented in the current release, the user is free to
> > use the values if he so wishes. It's not stupid, one never knows what the
> > next guy will do with ones code.
>
> It is mentioned
2009/10/20 :
>
> The comment on line 54 should perhaps be reworded to reflect that although
> it's not implemented in the current release, the user is free to use the
> values if he so wishes. It's not stupid, one never knows what the next guy
> will do with ones code.
It is mentioned in the docu
Hi Guys,
The Linux tthread.inc file in FPC 2.2.4 refers:
There is a constant array defined at line 55 that lists 'priority' values
which I think are inverted. i.e. Currently, the listed values range from -20
to +19 and these map to tpIdle to tpRealtime. According to man nice(1),
Nicenesses rang
On 19 Oct 2009, at 19:08, Bart wrote:
In the code that "translates" the "you did something nasty" to
runerror(some_exit_code) it may be possible to differentiate between
float and integer fault?
It is (on some platforms with some hacking).
This info could then be stored in some variable/obj
30 matches
Mail list logo
