[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
> No, because that SORT property is not added to user objects,
> only to the grabber "GrabberInfo" internal object, of which
> there is one per datafile saved by the grabber.
Ok, that's what I had understood before running into the apparent
contradiction.
> Try creating a datafile, with an object in it, and give it
> the property BACK, set to 0, then setup the grabber to use
> backups, then save the datafile, quit, rerun grabber, load
> the datafile back, and check the BACK property and whether
> the grabber is setup to backup or not. If both didn't change,
> then it's probably safe, and the wording is misleading.
Both are preserved :-) so you're certainly right. I just need confirmation
from another specialist of datafiles and I'll start testing your patch. And
I'll also add another new global property TRAN corresponding to the
transparency preserving feature Elias and I added to Allegro and the Grabber
about one year ago.
Meanwhile, here's the proposed change to grabber.txt:
--- cvsroot/allegro/tools/grabber.txt Thu May 31 09:48:02 2001
+++ allegro/tools/grabber.txt Tue Apr 9 22:57:46 2002
@@ -123,9 +123,9 @@
For autocropped bitmap objects, the amount of cropping at the top of
the image.
-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.
+You can use whatever other ID's you like to store custom information about
+your objects (the grabber internally use some other properties but they
+won't conflict with yours).
--
Eric Botcazou
ebotcazou@xxxxxxxxxx