[Xastir] Memory fixes, plus special stuff not in the docs

[Jason Hitesman]

WARNING: Unsanitized content follows.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Curt, WE7U wrote:

> On Thu, 24 Jun 2004, Curt, WE7U wrote:
>
>>On Thu, 24 Jun 2004, Jason Hitesman wrote:
>>
>>>Oddly enough the memory footprint on the Cygwin system went up, it was
>>>14Meg before now it's reporting 17Meg.  Still stable though it ran all
>>>day with no problems.
>>
>>Somewhere along the way I snuck in another text field to the
>>station records struct which holds the new tactical callsign.  I
>>suppose I could get busy and turn that into a pointer, allocating
>>the record if a tactical call was assigned.  We do similar things
>>elsewhere in that struct.
>
>
> I should be able to change that at lunchtime today:  Only the
> stations that have a tactical call assigned will get the memory
> malloc'ed to hold them.  The rest of the station records will have a
> NULL pointer, which will be a minimal hit to your memory use.

Wow, I knew people said xastir had a quick to respond development team
but this blows me away :)

I didn't even think it was that big of a deal, just kind of an info
point more than anything, but it's impressive to see it corrected before
I even realized it was something tha needed correcting!

I was going to stick to keeping xastir on my Linux box and abandon the
Cygwin but I guess I'll keep the Cygwin around for testing a little
longer now.

Somewhat off topic for this but concerning the Debian Sarge comments.
My Linux box is Debian Sarge and xastir is running great on there.  But
I'm using the Cygwin xserver on my windows box for display instead of
the local xserver (since that system has no monitor attached) if that
helps narrow down finding the 32bit display bug at all.

- ----
Jason Hitesman
N8INJ



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32) - GPGrelay v0.93

iD8DBQFA20KEQZ/FVX3rM0MRApMDAKCCh2yNoBo1KFPNVfXPUazQi8ApxwCfY+80
pynH5GvPEzHvIuoLNu3GFNU=
=tSUF
-----END PGP SIGNATURE-----