Treepad

[Bjorn Simonsen]

omega wrote in <[email protected]>:

Back to their web site, have you seen:
http://www.treepad.com/data/
and there the large freeware database (free4hjt.zip) for download?

Rather outdated (2001), so I followed the link
to the source <ftp://ftp.externet.hu/freepc/>
and there notice they have more recent

free5hjt.zip 2 487 KB 05.05.2002 00:00:00
free6hjt.zip 2 793 KB 03.08.2002 00:00:00

the file dates in the latter archive is Aug 2002...
so not very much more recent after all, but for the
curious....

All the best,
Bjorn Simonsen

 

[omega]

Looks like a tie: 9:24 AM on both our messages.

Yeah, we were both composing the same subj same time. Need my tinfoil hat.

yours had more info though. . .

Mine req'd 4+ cups coffee. I'm sure your own coffee|post ratios are far
more efficient.

 

[dszady]

Looks like a tie: 9:24 AM on both our messages.

yours had more info though. . .

Susan: 9:24:04
Karen: 9:24:44
It was a wonder that you guys didn't run into each other.

 

[omega]

omega wrote in <[email protected]>:

Back to their web site, have you seen:
http://www.treepad.com/data/
and there the large freeware database (free4hjt.zip) for download?

Rather outdated (2001), so I followed the link
to the source <ftp://ftp.externet.hu/freepc/>
and there notice they have more recent

free5hjt.zip 2 487 KB 05.05.2002 00:00:00
free6hjt.zip 2 793 KB 03.08.2002 00:00:00

the file dates in the latter archive is Aug 2002...
so not very much more recent after all, but for the
curious....

I once started a project of taking that freeware hjt file above, and
reorganizing it into categories. And also, trying to sweep out the crud:
lots of adware and similar insect life. I think I got to the D's. After
having logged about thirty hours or more. Then quit. It was just too much -
and too indiscriminate a file - to keep my interest.

I suppose it might be useful in some other way, as a reference dictionary,
if you need to look up a program by name. Find from it the website and
author's summary description. But for that use, it needs to be current.
And you've noted it's now over two years since update.

 

[omega]

Susan: 9:24:04
Karen: 9:24:44
It was a wonder that you guys didn't run into each other.

Well, I do have a slight bruise on my shoulder. Happened during the rush
to get the ball in the tether. I think the ump should call a foul. Set
back the :44 loss, then give me a free throw.

 

[Bjorn Simonsen]

I once started a project of taking that freeware hjt file above, and
reorganizing it into categories. And also, trying to sweep out the crud:
lots of adware and similar insect life. I think I got to the D's. After
having logged about thirty hours or more. Then quit. It was just too
much - and too indiscriminate a file - to keep my interest.

LOL! Been there, done that. Not with this particular file, but similar
"projects"...times over

And you've noted it's now over two years since update.

Quite so. Maybe a better served if simply downloading some ftp index
files from sites such as simtel/garbo/winsite and have those to stare
at instead 8->.

All the best,
Bjorn Simonsen

 

[omega]

Experience the same.

I think I'm having trouble understanding. The behaviour described here...

That's the behavior that I see. It's upon a save that it records the node
to which it will return at next open.

Btw, I investigated where it is storing that information. It's in the .knt
file itself.[*] Now, writing that position info upon save, that's the only
way I can see for it to be done. What I haven't been able to grasp is that
it would have previously done things any differently...

Or? Could it be a matter of earlier having one's auto-save settings set to
much more frequent intervals. Then the navigation position would be saved
more transparently.


--
Karen S.

_______
[*} A simple .knt test file, with four bare nodes.

third node selected:

CX=6
FL=101100000000200000000000
SN=2

first node selected:

CX=0
FL=101100000000200001000000
SN=0

 

[Bjorn Simonsen]

That's the behavior that I see. It's upon a save that it records the node
to which it will return at next open.

Maybe I have just misunderstood how it is supposed to work, don't know
how it worked before as I haven't used it that long. I assumed, if I
browse a database, reading NODE A, then close it, it should open in
NODE A again (last state) when I open it the next time - and not NODE
B or whatever (last edit). But instead it opens, as you describe, in
the Node I last edited, until the next edit/save.

All the best,
Bjorn Simonsen

 

[omega]

Maybe I have just misunderstood how it is supposed to work, don't know
how it worked before as I haven't used it that long. I assumed, if I
browse a database, reading NODE A, then close it, it should open in
NODE A again (last state) when I open it the next time - and not NODE
B or whatever (last edit). But instead it opens, as you describe, in
the Node I last edited, until the next edit/save.

It occurs to me this: If the programmatic design were such that the info
were recorded to the registry, instead of into the files, then tracking
navigation positions would not be dependent on saves. Although I would
not want that kind of registry dependency, nor all the fat hex values.

Increasing the auto-save interval, at our end, seems to me that it would
be the right solution.

Only...I just tested. And it did not have the same effect as a manual
save. Either my test was too impatient (tho sure seems I waited a full
two minutes). Or somehow the autosave in Keynote does something different
that the manual save command. ?? A strange idea for me to accept, but
then again, not a programmer, I can't assess...

 

[Bob Adkins]

I think I'm having trouble understanding. The behaviour described here...

It's simple. KeyNote is supposed to save on exit, including the current
node.

I have a suspicion that my KNT file is getting too fat.

Bob

Remove "kins" from address to reply.

 

[Bob Adkins]

Only...I just tested. And it did not have the same effect as a manual
save. Either my test was too impatient (tho sure seems I waited a full

I forgot the most important thing!

The node save USED to work all the time. Now it works seldom if at all.

Bob

Remove "kins" from address to reply.

 

[omega]

I have a suspicion that my KNT file is getting too fat.

No. The test file I used was less than 1k.

 

[omega]

The node save USED to work all the time. Now it works seldom if at all.

It sounds like your original plan of contacting Marek would be best.
Since he has his web forum, I don't expect him to stop by here.

The node position, it is not an issue to me. My wish for Keynote involves
the rename response, but I think I'm best waiting for the v2 development.