Build62 eats memory on Fujitsu T830

[madman]

When I try to run build 62 on my T830, it immediately grabs over 20MB of Program Memory. The T830 only has ~25MB RAM available after a soft reset, with no other tasks running. So Agendus either slows to a crawl, or locks up the machine compeletely. When I exit Agendus, I'm back to 24-25MB free. For comparison, Agenda One (my normal PIM) uses around 2.5MB. I have aproximately 2200 appointments and 550 contacts in my PIM (PIM.VOL is 5.6MB)

Looking forward to seeing this working as was a long time Palm Agendus user - but at the moment it won't even run long enough to test!

[fireman54]

Did you read the known issues?

Known Issues

- Meeting Attendees are currently not saved in the native Pocket Outlook Fields.
- Meeting Categories are not being loaded / saved from Pocket Outlook
- At times the application will start but remain in the background. If upon launch you don't see the AGWM windows, visit settings -> system -> memory -> running programs, then select "Agendus" and press the button "activate" to workaround the problem
:rolleyes: - Memory footprint becomes excessive in case of large amount of contacts and events.
- Over the air data retrieval: AGWM currently doesn't bring up the network connection, therefore will fail unless the connection is already established.

[madman]

Yes, but I didn't expect it to be _that_ excessive! With that and the known issues in category and attendee support, I guess I'll have another try when the code is actually at beta and not alpha stage (i.e. it's ready for testing on real data!)
Have a Happy New Year!

[fireman54]

Yes, it is that excessive. I had tried it out with the full compliment of my contacts and appointments. It had a cow. It is a bit rough right now. Many say it is too soon out of alpha. However, being a long time user of Action Names/Agendus, I think Iambic will eventually get most of the bugs out. Also, this is not a normal beta as everyone thinks. It is a pre-beta. As Iambic calls it, a Community Technology Preview. So, it was not released as a fully functional product. Progress is being made. Feel free to sample a later revision when more functionality is done and more bugs are squashed. Have a great new year.