[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
> I don't know. Probably not, since it's done by storing a property
> in the grabber specific object, and it should work as it did
> before when it is not found. I've been using it for quite a while
> now.
In light of (excerpt from grabber.txt):
"The properties "HNAM", "HPRE", "XGRD", "YGRD", "BACK", "DITH" and "PACK",
are also used internally by the grabber, but you can use whatever other ID's
you like to store custom information about your objects."
and:
--- allegro-3.9.34/tools/datedit.h Wed Jan 24 06:15:06 2001
+++ allegro34.v2/tools/datedit.h Sat Mar 17 11:43:29 2001
@@ -28,6 +28,7 @@
#define DAT_XSIZ DAT_ID('X','S','I','Z')
#define DAT_YSIZ DAT_ID('Y','S','I','Z')
#define DAT_PACK DAT_ID('P','A','C','K')
+#define DAT_SORT DAT_ID('S','O','R','T')
#define DAT_HNAM DAT_ID('H','N','A','M')
#define DAT_HPRE DAT_ID('H','P','R','E')
#define DAT_BACK DAT_ID('B','A','C','K')
Isn't that enough to break any datafile that already defines a SORT property
(disclaimer: I'm not a specialist at all of these datafiles) ?
--
Eric Botcazou
ebotcazou@xxxxxxxxxx