I have an early version for getting text, in Windows anyway.

a5_clipboard.h:

a5_clipboard_win.c:

Do you think I should add an option to limit the amount of text that is returned?
I still haven't figured how to get unicode text (like from character map) to show up correctly...even using ALLEGRO_USTR. Any suggestions?

Arbitrary limits are evil, so no, you shouldn't. But who is responsible for freeing the pointer returned by al_get_clipboard_text? If it's a static buffer that changes the next time GetClipboardData/GlobalLock are called, you should strdup it.

It should work AFAIK if you use a char * pointing to a UTF8 encoded string. Doesn't that work for you? Have you checked the encoding?

Demo not working for me (VS 2009). It stops when trying to load the sound file "big_explosion.ogg", although the file is in the proper place.

I don't think so. Is it a prerequisite for Allegro 5? or is it only for the demo?

Ok, libogg and libvorbis downloaded, compiled and installed.

What now? how do I add support for it for the demo? or is it automatic?

EDIT:

The code that fails is this one:

/* Function: al_load_sample
 */
ALLEGRO_SAMPLE *al_load_sample(const char *filename)
{
   const char *ext;

   ASSERT(filename);

   ext = strrchr(filename, '.');
   if (ext == NULL)
      return NULL;

The filename is "c:\dev\allegro-4.9.8\demo\data\sfx\big_explosion.ogg".

The function strrchr returns null, and therefore the sample can not be loaded.

Nope. I am about to do that again.

EDIT:

Bleh, I built libvorbis but cmake can't find it, although I added the correct paths...it's late, and I am tired of the the command line already. The command line sucks. No demo for me...

I was wondering if I could get some people to test this for me. I've noticed different behavior on two different machines, both with the same OS (Windows Server 2008). I am guessing this is a driver issue, maybe ATI Vs. nVidia . The main problem is that my ATI driver (at least in my mind so far) is causing this to fail when loading the Terrain.png file. I can not seem to get debug info from it either. The debugger says that there are no symbols for it...allegro was compiled with debug options as well as the program, so I assume that it is a failure in one of the other modules, perhaps something from DirectX. I can switch the Terrain.png to be a grid of 10x10 tiles and it works. It is almost as if it is running out of memory, but that can't be...I have over a gig in each machine and plenty of free memory. I am thinking it has something to do with texture memory and the way the two (nVidia and ATI) handle that. I am just trying to figure what the main deal is here. I've also noticed that on my ATI system, the drawing functions look different as well. The drawing functions look fine in other programs I've made between both systems, so that is weird. It is the exact same program, but the al_draw_rounded_rect looks different on both systems. It looks correct on my nVidia card, but the rounded rects look slightly scewed. If you decide to test this for me, please let me know what system (OS and version) and what kind of video card type and video memory your system has. Note: this was tested with Allegro-4.9.8, so that is why I am posting it here. I want to see if this is a bug with Allegro, or something with ATI or nVidia drivers.

Here is the Visual Studio 2008 project files, source code, and data needed.
Here is the 10x10 tile grid file that worked on the ATI system. If you would, please rename the original Terrain.png and put this to data/gfx/terrain.png in the programs search path. Please test with both versions and let me know if one worked and not the other, or if both worked/failed for you as well.

For those who do test it, spacebar pops up the terrain to 'select' (enter tile brush selection mode) and esc exits the program. When in 'select' mode, arrow keys move the selection cursor around, enter selects a tile brush, and esc exits that mode.

Thanks guys.:-*

Edit:
Here is a compiled version for Windows (using Visual Studio 2008).

The standard no screen shot, no download...so here ya go:
Main screen:
http://www.allegro.cc/files/attachment/598032
Tile brush select mode:
http://www.allegro.cc/files/attachment/598033

Anyone?! I want to see if this is something with the way the new API deals with hardware calls, or if it is a driver issue...and if it can be fixed. Maybe this could be addressed in the FAQ or other area.::)

allegro5.org has binaries.

Right now its purpose is news on Allegro 5 and Binaries. We (trent and I) don't really have much news to post...

Later on it will probably just be turned into an alias for liballeg.org once allegro 5 is released.

The FAQ seems to be working fine though. Its just that there are no questions

Yeah I like allegro5.org, has a good solid feel to it.
The design of it right now really looks like a place where you should be able to find all the resources you need with just one or two clicks. But I don't think you do quite yet, basically because some things people need haven't been written yet.

If anyone wants to work on the FAQ or any other areas of allegro5.org let me know. I can handle the binary releases.