|
|
Post by George on Oct 28, 2018 11:04:15 GMT -5
Robert: OK, the bottom legend seems to be missing L (I'll check that out), but otherwise it seems to be working fine, see attached screen shot. There is no special folder handling that would exempt AUTO. George Attachments:
|
|
|
|
Post by George on Oct 28, 2018 15:02:38 GMT -5
Robert: I had originally coded this using a cache to track STATE On/Off for a filetype, but you convinced me it wasn't worth it and could introduce this type of out-of-sync problem, so I yanked it. So it examines STATE right at Lines execution time.
Did you just not try the L command because it wasn't in the bottom Help lines? Command validation doesn't know/care what's in the Help lines. Maybe it would have worked. (I've corrected Help to show Lines for a Filepath display)
Or if you did try, it should have produced some kind of message good or bad. Did you get any?
George
|
|
|
|
Post by George on Oct 29, 2018 9:38:30 GMT -5
Robert: So when you got the message "File STATE information updated", the Lines count didn't appear right beside it? Works fine here.
If so, I have no ideas, the relevant code lines are adjacent.
AFList(i).LinesInt = sGetLines(fn) ' Get Line count from STATE
AFList(i).Msg = "File STATE information updated." ' Tell user
|
|
|
|
Post by George on Oct 30, 2018 11:10:14 GMT -5
Robert: My brain is giving out, going to have to give all this up.
I said the cache code had been removed - if fact it hadn't, and it was not even fully implemented. I would have bet good money that I'd done the removal.
The cache support was still there, but the reset cache function was never getting called by anyone. So I added the reset call to the STATE command processing, and all is now well.
So yes, right now it takes an SPFLite restart to allow the LINES command to "see" recent STATE changes.
George
|
|
|
|
Post by George on Oct 31, 2018 11:58:34 GMT -5
Robert:
Yeah, but I'm more seriously thinking of an actual "retirement" from this. My whole body is slowly packing it in, everything is now a struggle to do. I'm thinking of doing a release with the registration and web version check removed. Then just calling a halt to further work.
It's been a great run, but it's becoming time to end it.
George
|
|
|
|
Post by George on Nov 1, 2018 11:16:43 GMT -5
Robert:
Getting anyone to 'take over' is just a dream. PowerBasic is hardly mainstream, there are very few programmers, and who would tackle becoming familiar with 60K+ lines of code - with no expectation of reward.
"Retirement lite" might be OK, no commitment to fix things, just a "Maybe I'll look at it".
I think I'll still remove registration and website version checking. Maybe I'll also ZIP up the development folder and make the source available on the download page. Anyone want it? Fine, take it and good luck!
That way I can just keep paying to keep the SPFLite.COM site going as long as I'm able. When I stop paying, 1and1.com will just shut everything down.
George
|
|
|
|
Post by nicc on Nov 4, 2018 2:46:03 GMT -5
I would not mind having a peek at the code so if it were to be bundled and put on the download page I would download it. Wouldn't do anything with it except try to figure out the architecture.
If the code were available some bright spark might pick it up as a hobby and it may get down through generations thus you would have a legacy. You would have to change the licencing to whatever so that others can amend and distribute.
It's not dying, it is moving on to another plane of existence. I simply hope that, in my case, I do this move by simply going to sleep one night and forget to wake up next day!
|
|
|
|
Post by George on Nov 4, 2018 13:47:25 GMT -5
Robert: Nicc: Yes, this end of life planning is no fun. I can't look to Linda, her eyes are failing (macular degeneration - she's already had her driving license pulled) plus the knowledge just isn't there. My sons (both almost 50) are typical of today's generation, too wrapped up in their own lives.
I think tidying it up, making the source available etc. then paying for a few years of web hosting is the simplest approach.
George
|
|
