You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(40) |
Aug
(83) |
Sep
(1) |
Oct
(2) |
Nov
(2) |
Dec
(8) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(12) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
From: Stijn W. <st...@xs...> - 2003-10-21 14:30:22
|
confirm 384868 |
From: Peter W. <tj...@al...> - 2003-06-19 01:34:16
|
Nearly a year on, I've finally deleted this list. Apparently, you can still post here, but the list doesn't show up on the SF.net project page. --=20 =E7=8E=8B=E6=B5=A9=E7=A6=8E |
From: Matthew S. <ma...@th...> - 2002-07-11 16:48:58
|
Just a little question about style The scrollbars in a multiline textbox, should these be internal to the object? I guess they should but does everyone else do this? Also, maybe an answer for jrschnayer. The mac uses plain CR as a line ending. The utilities for converting between Windows(CR,LF) and Linux (plain LF) are called dtou and utod. Look for utilities called mtou and utom to convert the makefile and source files to mac-OS format. I guess the fix.sh script should have done this for you, have you run that before make? -- Matt |
From: Sven S. <Sve...@st...> - 2002-07-11 09:50:06
|
> I was refered to this mailing list because it seems nobody on > allegro.cc could solve my problem(probably because I am one of the > only people to ever try to install the mac version of allegro). I don't know the answer of your problem, but you'd probably rather ask at the allegro mailing list (al...@ca...; see http://alleg.sourceforge.net/maillist.html). This mailing list is specifically for some GUI-related add-on libraries for Allegro. al...@ca... is for your type of problems (and have more people to help you, too). Also, mention which version of Allegro you are using. Sven Sandberg |
From: <jrs...@uc...> - 2002-07-11 08:59:54
|
I was refered to this mailing list because it seems nobody on allegro.cc could solve my problem(probably because I am one of the only people to ever try to install the mac version of allegro). when i ran fixmpw.sh through mpw i got the following message ### Allegro var not defined correctly ### If required quit MPW after install ### Set - Too many parameters were specified. # Usage - Set [name [value]] ### MPW Shell - Execution of fix terminated. I deleted lines and ran the script and I think I got parts of it to run(i don't know anything about mpw scripts) I looked at the file makefile.mpw with the MPW compiler and it displays the whole file on one line without any carridge returns. As a result the whole thing is one big comment because the first character is a #. Ironicaly the makefiles for other compilers display correctly. So I think this is part of my install problem. Maybe I need a new copy of the script that isnt in the standard alleg distribution package. please help any way you can i have installed allegro on dev_c++ and djgpp without any trouble in the past |
From: Peter W. <tj...@al...> - 2002-06-11 01:23:36
|
On 2002-06-10, Matt Smith <ma...@th...> wrote: > How much trouble is it to leave it idle? Less trouble than closing it down. > If we can persuade Matt Leverton to create a new forum on allegro.cc ju= st > for GUIs then I would be happy to see this list close, but not otherwis= e. We can open this list to general GUI-related matters. I think if the guibrella project is dead, we should say so. It can be resurrected at any time, but as it is, I cannot cross it off my todo list :-) --=20 =E7=8E=8B=E6=B5=A9=E7=A6=8E |
From: Matthew S. <ma...@th...> - 2002-06-10 07:29:10
|
On 2002-06-06, Laurence Withers <lwi...@lw...> wrote: >> Since it seems that this list is dead :-(, I propose that we close it. >> Although the guibrella was a nice idea, it seems as though we don't >> have the time and/or interest to implement it. From: "Peter Wang" <tj...@al...> >Unfortunately so, or perhaps it was too much to hope the libraries could >remain independent. I'll close the list post-World Cup, unless >something comes up beforehand. How much trouble is it to leave it idle? There is no other forum for discussing the Allegro GUI. I have been struggling recently but I do have a new release on the way. If we can persuade Matt Leverton to create a new forum on allegro.cc just for GUIs then I would be happy to see this list close, but not otherwise. That new skinnable GUI by spellcaster is another candidate for folding into the project, but I don't think he knows about this list. I would like to run a server specifically for this myself but I'm having financial difficulties at present. I have the archive, but I haven't worked out how to turn the OE inbox into SQL yet. -- Matt |
From: Peter W. <tj...@al...> - 2002-06-07 00:53:28
|
On 2002-06-06, Laurence Withers <lwi...@lw...> wrote: > Since it seems that this list is dead :-(, I propose that we close it.=20 > Although the guibrella was a nice idea, it seems as though we don't=20 > have the time and/or interest to implement it. Unfortunately so, or perhaps it was too much to hope the libraries could remain independent. I'll close the list post-World Cup, unless something comes up beforehand. --=20 =E7=8E=8B=E6=B5=A9=E7=A6=8E |
From: Laurence W. <lwi...@lw...> - 2002-06-06 11:22:11
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, Since it seems that this list is dead :-(, I propose that we close it. Although the guibrella was a nice idea, it seems as though we don't have the time and/or interest to implement it. Personally, I have been working on my own GUI system which I now use in any Allegro program requiring a GUI, so Allegro's own system is no longer important to me. I guess other people find themselves in a similar position. Bye for now, - -- Laurence Withers, lwi...@lw... (GnuPG 04A646EA) http://www.lwithers.demon.co.uk/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE8/0ZuUdhclgSmRuoRAoA2AJ0XGLTKxrPiWEkLYFJE3oPTG+AnXQCfVbfz jX9uEajphXOmgXrL4IhnaoI= =/0AP -----END PGP SIGNATURE----- |
From: Sven S. <svs...@st...> - 2002-02-09 21:14:01
|
Matthew Smith wrote: > > and moreover, that package also creates libdime.a. > > Sue! Hehe, the other library that was actually first, and is probably bigger and more widely used so it seems very risky :-) > al_dime? dimez? diez? diegomaradona? > > I wouldn't change it so its totally unrecognisable. It's a Good Thing for me, because it's easier to search and replace if the old name isn't a substring of the new name :-) Oh, well, maybe adime, then? This looks like a pretty much abandoned combination of letters, too, and it will even have a meaning (allegro dialogs made easy). It's nice if it fits the 5 letter limit (libadime.a under dos). -- Sven Sandberg svs...@st... home.student.uu.se/svsa1977 |
From: Matthew S. <ma...@th...> - 2002-02-05 13:20:03
|
> and moreover, that package also creates libdime.a. Sue! > > The only solution I can think of is to rename Dime (our one). My > suggestion is Zqq (for no other reasons than google's inability to find > something relevant with that name: It should be pretty unlikely that > this happens again with that name). Any objections or better ideas? al_dime? dimez? diez? diegomaradona? I wouldn't change it so its totally unrecognisable. |
From: Sven S. <svs...@st...> - 2002-02-05 12:47:36
|
Hello, The good news is that Dime is now finally shipped with a real Linux distro, namely Debian. The bad news is that this is something completely different than our gui add-on for Allegro (see http://www.coin3d.org/Dime/about.xml) :-(. So there's a name conflict, and moreover, that package also creates libdime.a. The only solution I can think of is to rename Dime (our one). My suggestion is Zqq (for no other reasons than google's inability to find something relevant with that name: It should be pretty unlikely that this happens again with that name). Any objections or better ideas? -- Sven Sandberg svs...@st... home.student.uu.se/svsa1977 |
From: Eric B. <ebo...@li...> - 2002-01-21 19:15:29
|
> Thank you very much! It's really nice. I uploaded it as AGUP 0.6. I've forgotten one thing because I coded it under QNX, but examp.c doesn't work for me under Windows because of the 15-bit/16-bit color issue. Btw, is the horizontal slider the right one, under GTK+, Win95 and Photon ? For example, I've attached another Win95 slider (msctls_trackbar32 from commctrl.h) that seems to be more suited to the situation. -- Eric Botcazou ebo...@mu... |
From: Peter W. <tj...@al...> - 2002-01-20 01:52:14
|
On 2002-01-18, Eric Botcazou <ebo...@li...> wrote: > Hello Peter, > > I'm currently in my QNX period ;-) and I took a little time to contribute to > the Grand Un-uglification Project. The result of this work is attached. Thank you very much! It's really nice. I uploaded it as AGUP 0.6. > I found a little glitch when coding the menu functions: gui_draw_menu() > doesn't provide enough bits from the underlying MENU_INFO structure, so I > had to devise a little hack. > > The code is not particularly clean nor optimized, but it sort of works :-) (shrug ;) |
From: Matthew S. <ma...@th...> - 2002-01-11 04:34:40
|
> > http://www.the-good-stuff.freeserve.co.uk/allegro/gui/mage/mage041_s.tar.gz > > "The requested URL /allegro/gui/mage/mage041_s.tar.gz was not found on this server." > It is now. Freeserve have a seperate upload server, it must have crashed before making it onto the download one. I checked it this time. |
From: Peter W. <tj...@al...> - 2002-01-11 01:19:40
|
On 2002-01-11, Matthew Smith <ma...@th...> wrote: > I just found the new gui_* hooks for the built-in widgets :) > That'll make things easier. I can go and change all my mage_button_proc's > to d_button_proc again. Actually, they were made only for the file selector and alert boxes. Internally these dialogs use _gui_*. The gui_* hooks don't do anything for d_*_proc. > What I'm tempted to do is have negative values for d->bg to be indexes to > bitmaps in the skin .dat, but that might cause problems (although I cant > think of any offhand). This is on the verge of evil :-) I would suggest a simple array of BITMAPs instead of a DATAFILE. Negatives numbers might conflict with some uses of makecol(). |
From: Matthew S. <ma...@th...> - 2002-01-11 00:08:28
|
Sorted. http://www.the-good-stuff.freeserve.co.uk/allegro/gui/mage/mage041_s.tar.gz I decided to test with DJGPP and found that -Wall doesn't do the job with MingW32. exdraw1 segfaults in DOS, but the rest work in spite of the warnings. I'll tackle those I can deal with ASAP. I just found the new gui_* hooks for the built-in widgets :) That'll make things easier. I can go and change all my mage_button_proc's to d_button_proc again. I'm going to put bitmap skins on everything next, because that's what the kids want most anxiously. I might as well do the translucent widgets too, as they will look good over the skins. What I'm tempted to do is have negative values for d->bg to be indexes to bitmaps in the skin .dat, but that might cause problems (although I cant think of any offhand). I can leave that for now and just have common bitmaps for object types, that's a good start. |
From: Peter W. <tj...@al...> - 2002-01-09 23:57:22
|
On 2002-01-09, Matthew Smith <ma...@th...> wrote: > before I post it, I have a couple of linuxy questions > > 1) Should CFLAGS include -L/usr/local/lib ? Unnecessary, but it doesn't hurt. > 2) How can I get the users home directory into a string? (for browsing with > al_find*) getenv("HOME") |
From: Matthew S. <ma...@th...> - 2002-01-09 20:56:56
|
Ok, I've tidied things up and I get no warnings with -Wall on mingw32. I've extern'ed most of the globals in the headers and declared them again in the .c files. I've removed the #include "dir.h" as it isn't needed anymore I've fixed the makefile to build 6 example programs including a significant new one. exfsel1 shows a collapsing folder tree in the left pane, and a file list in the right, à la Windows Explorer. The folder tree uses a general purpose tree widget which can be used for any hierachical data. The file list is shown with a datalist widget which is flexible enough to display tables and spreadsheets. before I post it, I have a couple of linuxy questions 1) Should CFLAGS include -L/usr/local/lib ? 2) How can I get the users home directory into a string? (for browsing with al_find*) |
From: Peter W. <tj...@al...> - 2002-01-09 02:19:18
|
On 2002-01-06, Matthew Smith <ma...@th...> wrote: > This release is mostly to give the source code for the paint program. Also > it builds a libmage0.a and links the examples to that. This won't install > the lib on Linux because I wasn't sure where to. I have since learned that > /usr/lib is the standard place so the next version will bung it in there. It should go in /usr/local/lib by default. > I'm going to work on tree.c next which will be like MFCs CTreeView. Then > mage v.1 will be about complete and I can get on with the dialog editor and > other tools and demos. > > http://www.the-good-stuff.freeserve.co.uk/allegro/gui/mage/mage04_s.tar.gz I couldn't compile it, firstly because dir.h doesn't exist under Linux, then lots of warnings. Use `extern', Matt! And proper includes. |
From: Matthew S. <ma...@th...> - 2002-01-06 14:50:32
|
This release is mostly to give the source code for the paint program. Also it builds a libmage0.a and links the examples to that. This won't install the lib on Linux because I wasn't sure where to. I have since learned that /usr/lib is the standard place so the next version will bung it in there. I'm going to work on tree.c next which will be like MFCs CTreeView. Then mage v.1 will be about complete and I can get on with the dialog editor and other tools and demos. http://www.the-good-stuff.freeserve.co.uk/allegro/gui/mage/mage04_s.tar.gz |
From: Matthew S. <ma...@th...> - 2002-01-04 13:29:02
|
oops yeah, sorry. I'm still using OE. I'll switch when I find a way to convert my inboxes to something else. |
From: Peter W. <tj...@al...> - 2002-01-04 12:52:27
|
Dunno if Matt meant this for this for the list. ----- Forwarded message from Matthew Smith <ma...@th...> ----- Extra messages don't interfere with anything. It would be implemented in the dialog player. This is upgradable already so I'll implement it that way for now. I'll have static cx & cy in the dialog player instead of the widgets and reset them to -1,-1 when the focus changes. I'm doing widgets that draw themselves according to global style variables now. I think this is more user friendly than the agup method but is obviously a bit bulkier and slower, but I think it's worth it, as the GUI appearance can be changed at run-time. If Laurence doesn't mind, I'll do stylable versions of his widgets in my library. It's easier to combine them that way rather than calling his lib, as I need to double-buffer a lot of stuff. I'll also make an agup set which wrap calls back into my lib so programs written to use agup will work straight away with mine. I've messed up my library API a tiny bit to get the paint demo running but I'll fix up the other demos and post the source soon. I meant to get this all working while you were all busy with Allegro 4, but I lost the plot for a while, unfortunately. The layoff did me good though. ----- End forwarded message ----- |
From: Peter W. <tj...@al...> - 2002-01-03 12:50:02
|
On 2001-12-28, Matthew Smith <ma...@th...> wrote: > A MSG_MOVEMOUSE would be neat. One of the bits in the flags could be used > to request them, or they could be sent to whichever widget has the focus. > What I'm doing in my big widgets is this. It works but it means I can only > have one of these widgets at a time, and the syntax isn't as sensible as > MOVEMOUSE would be. Hmm, how would this be implemented, given that we can't extend the DIALOG structure? If only the widget with focus gets them, then something usable should be possible by wrapping get_mouse_mickeys() slightly. I didn't think about it for long though. BTW, AGUP 0.5 is available (nothing really major). |
From: Matthew S. <ma...@th...> - 2001-12-28 11:41:22
|
A MSG_MOVEMOUSE would be neat. One of the bits in the flags could be used to request them, or they could be sent to whichever widget has the focus. What I'm doing in my big widgets is this. It works but it means I can only have one of these widgets at a time, and the syntax isn't as sensible as MOVEMOUSE would be. d_foo_proc(,,) { static int cx,cy; case MSG_GOTMOUSE: cx=mouse_x; cy=mouse_y; case MSG_IDLE: if ((cx != mouse_x) || (cy != mouse_y)) { mousemovestuff } cx=mouse_x; cy=mouse_y; } |