[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
>Also, my todo list reminds me that I need to try to find some way of
fixing
>the fact that datafile password encyrption isn't very smart, and I have
a
>feeling that these two jobs might have a common solution. I'm not
hugely
>fussed about getting this done for 4.0, but it would be nice to sort
out.
Looking at this again, I remind something I thought would be cool: I
have
a game which uses two kinds of packfiles: one for game data, one for
save
game files. I want a password for the game data ones, and I want another
one (actually I would dynamically generate it :)) for save game files.
The
problem is that I load data from the first type when loading saved game
from the second type. And this causes problems because the password
system
is global to all packfiles. I could easily get around it, and that is
what
I did, but I think it would be cleaner to get this done in the lib. If I
recall well, it would just be a matter of adding a password field in the
packfile structure. Maybe some other caveats, though, I did not look far
enough to know.
Any comments ?
--vp
Windows is slow and crashaholic ? Linux is too hard to learn ? Try BeOS
!