I believe I have fixed this bug in CVS, but it will still
exist in version 0.0.4 or earlier. Hense there will
*definately* be a 0.0.4-1 release with this bugfix along
with other fixes, assuming I can verify this error. I am
unable to verify that this is fixed yet.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=64543
I believe I have fixed this bug in CVS, but it will still
exist in version 0.0.4 or earlier. Hense there will
*definately* be a 0.0.4-1 release with this bugfix along
with other fixes, assuming I can verify this error. I am
unable to verify that this is fixed yet.