| Title: | TDL - To Do List handler |
| Moderator: | PLAYER::BROWNL |
| Created: | Thu Sep 30 1993 |
| Last Modified: | Tue Dec 12 1995 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 102 |
| Total number of notes: | 424 |
Due to (unrealized) limitations in Visual Basic, you cannot store more
than 129 items. This needs to be fixed with a change in
architecture...for now, I've built a version that allows 50 extra items
to be stored (shout if you need it). Other workaround is to delete
closed items.
This is a pisser, and a direct consequence of using Basic over C. Come
on Microsoft, where's Visual C?!?!?!
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 63.1 | SBPUS4::Mark | Tue Jul 28 1992 12:40 | 3 | ||
Make the retention of closed lines a setable option. Something like a little box on the close confirm. (Like the save options on exit box was on MSWin 3.0) | |||||
| 63.2 | SAC::EDMUNDS | Sh ot | Tue Jul 28 1992 13:13 | 2 | |
How do you see differentiation between Close and Delete if you -don't-
retain closed items?
| |||||
| 63.3 | SBPUS4::Mark | Tue Jul 28 1992 13:18 | 3 | ||
Because I never want to keep deleted lines. I may or may not want to keep closed. | |||||
| 63.4 | SAC::EDMUNDS | Frog, earwig, earwig | Mon Oct 26 1992 17:58 | 4 | |
Visual Basic restriction in V1. Fixed in V2 (out very soon). As soon as
I can get hold of a copy of V2, you'll have a fixed version. For now
(X.107), a precentage monitor shows how much of the database space
you've used.
| |||||