I'm writing a program who's main function will essentially boil down to
copying a small rectangle from one image to another and write it out as
a JPG file. No other image manipulation functions are required. It
does have to be as absolutely speedy fast as possible, so I was
wondering if anyon
* Felix Breuer ([EMAIL PROTECTED]) wrote:
> Hello,
>
> the CVS version of evas won't build, because of the not-implemented
> xrender engine. Why is the xrender engine in the configure.in and
> Makefile.am files even though that engine does not exist yet (making
> it impossible to build evas from C
On Thu, 15 Dec 2005 10:32:44 +0800 Phuah Yee Keat <[EMAIL PROTECTED]> babbled:
> Carsten Haitzler (The Rasterman) wrote:
> > On Thu, 15 Dec 2005 10:14:41 +0800 Phuah Yee Keat <[EMAIL PROTECTED]>
> > babbled:
> >>I have checked the way KDM does autodetection of the sessions that are
> >>available
Carsten Haitzler (The Rasterman) wrote:
> On Thu, 15 Dec 2005 10:14:41 +0800 Phuah Yee Keat <[EMAIL PROTECTED]> babbled:
>>I have checked the way KDM does autodetection of the sessions that are
>>available on the system, it uses its own set of ".desktop" files (which
>>we can just copy), and chec
On Thu, 15 Dec 2005 10:14:41 +0800 Phuah Yee Keat <[EMAIL PROTECTED]> babbled:
> Hi,
>
> I have checked the way KDM does autodetection of the sessions that are
> available on the system, it uses its own set of ".desktop" files (which
> we can just copy), and check to see if the executables are
Hi,
I have checked the way KDM does autodetection of the sessions that are
available on the system, it uses its own set of ".desktop" files (which
we can just copy), and check to see if the executables are in the system.
I have did a quick check on the e_libs, but sees no library to parse
.d
On Wed, 14 Dec 2005 16:44:17 + Foxy <[EMAIL PROTECTED]> babbled:
> Felix Breuer wrote:
> > Hello,
> >
> > the CVS version of evas won't build, because of the not-implemented
> > xrender engine. Why is the xrender engine in the configure.in and
> > Makefile.am files even though that engine does
On Wed, 14 Dec 2005 08:35:48 + Felix Breuer <[EMAIL PROTECTED]> babbled:
> Hello,
>
> the CVS version of evas won't build, because of the not-implemented
> xrender engine. Why is the xrender engine in the configure.in and
> Makefile.am files even though that engine does not exist yet (making
Foxy wrote:
the CVS version of evas won't build, because of the not-implemented
xrender engine. Why is the xrender engine in the configure.in and
Makefile.am files even though that engine does not exist yet (making
it impossible to build evas from CVS)?
Assuming there is some reason to the above
There is a working xrender engine in CVS now.On 12/14/05, Felix Breuer <[EMAIL PROTECTED]> wrote:
Hello,the CVS version of evas won't build, because of the not-implementedxrender engine. Why is the xrender engine in the configure.in andMakefile.am
files even though that engine does not exist yet (
Felix Breuer wrote:
Hello,
the CVS version of evas won't build, because of the not-implemented
xrender engine. Why is the xrender engine in the configure.in and
Makefile.am files even though that engine does not exist yet (making
it impossible to build evas from CVS)?
Assuming there is some rea
Hello,
the CVS version of evas won't build, because of the not-implemented
xrender engine. Why is the xrender engine in the configure.in and
Makefile.am files even though that engine does not exist yet (making
it impossible to build evas from CVS)?
Assuming there is some reason to the above: what
On Wednesday 14 December 2005 05:04, Morten Nilsen wrote:
> Phuah Yee Keat wrote:
> > else
> > {
> > +#if DEBUG
> > fprintf (stderr, "Unknown string %s\n", down->keyname);
> > +#endif
> > }
>
> wouldn't it be better if the #if was moved above else?
>
> the compiler probably
Phuah Yee Keat wrote:
Morten Nilsen wrote:
wouldn't it be better if the #if was moved above else?
the compiler probably optimizes it away anyway, but..
Hmm, it din really occur to me...sorry for missing that. I guess this
change doesn't need a patch from me eh? :)
it's easy to miss such th
Morten Nilsen wrote:
Phuah Yee Keat wrote:
else
{
+#if DEBUG
fprintf (stderr, "Unknown string %s\n", down->keyname);
+#endif
}
wouldn't it be better if the #if was moved above else?
the compiler probably optimizes it away anyway, but..
Hmm, it din really occur
Phuah Yee Keat wrote:
else
{
+#if DEBUG
fprintf (stderr, "Unknown string %s\n", down->keyname);
+#endif
}
wouldn't it be better if the #if was moved above else?
the compiler probably optimizes it away anyway, but..
Cheers,
--
Morten
:wq
-
16 matches
Mail list logo
