Allegro 4.2.0 RC2 is released

Allegro 4.2.0 RC2 is released

Kitty Cat

Member #2,815

October 2002

Only the intptr types? :-/ Can't make anything easy, can they..

--
"Do not meddle in the affairs of cats, for they are subtle and will pee on your computer." -- Bruce Graham

CGamesPlay

Member #2,559

July 2002

All of the <u>int*_t types are automatically defined (except for 64 bit). No include file, from my experience. From a project that uses all the integer typedefs, here's some code:

//typedef __int8 int8_t;
//typedef unsigned __int8 uint8_t;
//typedef __int16 int16_t;
//typedef unsigned __int16 uint16_t;
//typedef __int32 int32_t;
//typedef unsigned __int32 uint32_t;
typedef __int64 int64_t;
typedef unsigned __int64 uint64_t;

That is, I used to have all of them defined, but I commented them out when I last used this code. Perhaps because I got a newer version fo the compiler. You'll have to do more research.

--
Tomasu: Every time you read this: hugging!

Ryan Patterson - <http://cgamesplay.com/>

Evert

Member #794

November 2000

Just a quick remark on the missing public RC1. I uploaded the files the evening before going on vacation but didn't announce the release because we wanted to have binary releases too. A few bugs showed up, and since these were fixed or had patches waiting by the time I got back, I didn't see much point in bringing out RC1 with known problems.

In the mean time, I'm having fun at a workshop in Chicago. Thanks to Matthew ands Peter for taking care of this baby!

Peter Hull

Member #1,136

March 2001

For the first time, we also have a Mac OSX binary installer. This will install

The Allegro library in normal, debug, profile and normal-static link versions
The grabber, dat and fixbundle tools
The help in Apple help-book format

If you are able, please try it out as I would welcome feedback.

OSX Installer (2.4MB)

Pete

Wil Renczes

Member #5,921

June 2005

Suggestion: for the msvc binaries at any rate, could someone include the .pdb symbol files with the binaries? That would be hugely helpful...

Matthew Leverton

Supreme Loser

January 1999

I assume alld42.pdb is the only one needed?

--
RTFM | Follow Me on Google+ | I know 10 people

Wil Renczes

Member #5,921

June 2005

actually, it would be nice to have both. Last night, I was hitting a crash while using the release lib... just makes it easier to pull up source when a problem occurs.

(BTW, the problem was nothing to do with Allegro, just a linking conflict between one component using debug vs another using release)

Gerwin Broers

Member #3,681

July 2003

I tried out the 4.2.0 rc2 yesterday, on win32/msvc. Mainly hoping for a "working" mouse speed setting. (Some guy was able to emulate my game on linux properly except for a super sensitive mouse behaviour). Am I right when concluding it has not been fixed? The mouse sensivity remained the same.

void set_mouse_speed(int xspeed, int yspeed);
Sets the mouse speed. Larger values of xspeed and yspeed represent slower mouse movement: the default for both is 2.

The game compiled and played fine mostly. Some Dialog drawing routines seemed a little messed up. I did not manage to fix these issues yesterday. But that could be caused by the tweaked dialog routines inside my game's libraries.

For now I just retained my 4.0.3 installation.

Main Project: HeroQuest. And Other Stuff

Steve McCrea

Member #5,954

June 2005

This is probably a stupid question, but how do you avoid these errors when including <allegro.h> in a cpp file?

C:\app\vs\VC98\INCLUDE\allegro/inline/draw.inl(67) : error C2562: 'vline' : 'void' function returning a value
C:\app\vs\VC98\INCLUDE\allegro/inline/draw.inl(67) : see declaration of 'vline'

Thanks,
Steve

Ok, it was stupid. I guess this is the solution:

#define ALLEGRO_NO_VHLINE_ALIAS
#include <allegro.h>

Matthew Leverton

Supreme Loser

January 1999

Those have already been fixed in CVS.

--
RTFM | Follow Me on Google+ | I know 10 people

Ariesnl

Member #2,902

November 2002

So... Now I can just use a package with MSVC 6.0 and it should work ?

man this is great..

I could use a decent IDE and debugger(MSVC) or I could use allegro and DEV-C++

so nog I can use Allegro AND MSVC .. great

Perhaps one day we will find that the human factor is more complicated than space and time (Jean luc Picard)
Current project: [Star Trek Project ] Join if you want ;-)

Milan Mimica

Member #3,877

September 2003

Just to let you down:
It is possible that MSVC support will be dropped in the next major release (4.3.0)

Vote against, if anyone asks you.

--
M.M.
http://sparklet.sf.net

Matthew Leverton

Supreme Loser

January 1999

MSVC support won't be droppped, although version 6 won't work if C99 is used.

You can either upgrade your command line tools (for free) and use them with the MSVC 6 IDE or download the (currently) free VC++ Express version, which contains a fully optimizing compiler.

--
RTFM | Follow Me on Google+ | I know 10 people

Evert

Member #794

November 2000

Quote:

It is possible that MSVC support will be dropped in the next major release (4.3.0)

No way. I'd personally love to drop active support for compilers that don't support C99 (and that includes all versions of MSVC), but dropping support for MSVC is just out of the question.

Ariesnl

Member #2,902

November 2002

It's not that I like microsoft so much .. It's I like having a debugger
just try debugging in Dev-C++

by the way .. MSVC moans about this

1bool Comp(const TSprite *v1, const TSprite *v2); 
2 
3 
4void TEngine::draw()
5{
6  draw_stars();     
7  
8  zero_sound=false;
9  items.sort(Comp);
10  list<TSprite *>::iterator p=items.begin();
11  while (p!=items.end())
12  {
13    TSprite*hulp=*p;
14    hulp->draw(x,y,vscr);
15    p++;                  
16  }
17  
18}
19 
20bool Comp(const TSprite *v1, const TSprite *v2) 
21{
22return (v1->z < v2->z);
23}

it's my Z_sort code in Dev-C++ it worked fine

Perhaps one day we will find that the human factor is more complicated than space and time (Jean luc Picard)
Current project: [Star Trek Project ] Join if you want ;-)

Milan Mimica

Member #3,877

September 2003

Evert: I can't say I understand you. You'd like to drop it, but it wont happen? Or is the active crucial here?

--
M.M.
http://sparklet.sf.net

Elias

Member #358

May 2000

There are things which would make maintanance easier, so we would like to do them. But we can't. MSVC support is one of them It definitely never was planned to drop support for MSVC > 6. MSVC-6 (as well as gcc 2.95) probably won't be able to compile future Allegro code, as well as any other sane open source project's code I believe. 4.2.0 should support both though.

--
"Either help out or stop whining" - Evert

Carrus85

Member #2,633

August 2002

Quote:

No way. I'd personally love to drop active support for compilers that don't support C99 (and that includes all versions of MSVC), but dropping support for MSVC is just out of the question.

Quote:

Evert: I can't say I understand you. You'd like to drop it, but it wont happen? Or is the active crucial here?

Milan: the problem is that, whether we like it or not, MSVC is basically the industry standard development tool for anything windows related. Dumping MSVC support would be, basically, committing library suicide. So, we'll have to be very careful if we ever do decided to dump support for MSVC. Frankly, I don't think we are ready to dump it quite yet. (4.3? We will see...)

Evert

Member #794

November 2000

Quote:

I can't say I understand you. You'd like to drop it, but it wont happen? Or is the active crucial here?

I'd like to drop active support, which means not doing anything in particular to make sure it compiles with MSVC. Not doing that means that it will probably get broken, but not nescessarily. Sticking to a well-defined standard should make the code work on all compilers that support that standard, but in practice it doesn't always work that way.
So while I'd personally like to say `here's our code, try if it works in MSVC, if it doesn't, tough', that won't happen.

Matthew Leverton

Supreme Loser

January 1999

It's not a matter of dumping support for MSVC, but MSVC dumping support for C. At the rate MSVC is deprecating standard C features, it won't be too surprising to see it drop C completely.

While some parts of C99 are nice, I don't think it's worth it to switch to it yet. What is gained is trivial to losing a large audience. I believe a language switch to C99 would have to be an Allegro 5 thing. Because by that time Microsoft probably will only be in the C# business anyway.

--
RTFM | Follow Me on Google+ | I know 10 people

Evert

Member #794

November 2000

Quote:

What is gained is trivial to losing a large audience.

Yes, I agree.

Paul Pridham

Member #250

April 2000

Crap. I use MSVC 6.

----
<:=
The Sword of Fargoal -- Saucelifter -- www.saucelifter.com

Ceagon Xylas

Member #5,495

February 2005

:strokes it:
Thanks guys!!

Ariesnl

Member #2,902

November 2002

Quote:

It's not a matter of dumping support for MSVC, but MSVC dumping support for C. At the rate MSVC is deprecating standard C features, it won't be too surprising to see it drop C completely.

hum by that time someone should make a opensource IDE for GCC/MingW with an integrated debugger and code completion..

Perhaps one day we will find that the human factor is more complicated than space and time (Jean luc Picard)
Current project: [Star Trek Project ] Join if you want ;-)

Corelian

Member #3,376

March 2003

Quote:

hum by that time someone should make a opensource IDE for GCC/MingW with an integrated debugger and code completion..

MinGW Developer Studio, not perfect but nice. I tried it maybe a year ago. The debugger is very much like the one in Visual Studio and the source editor uses Scintilla.