History lists question

[Carlo Hogeveen]

Sammy,

The context is, that I attempt to write an extension that will fix, that for concurrently opened TSE sessions only the history lists of the last closed session are remembered for future TSE sessions.

My first attempt was doing this using the macro language's history commands, but they are too slow:
I am currently running a test where all history lists are empty, and filling them to the max (65535 entries) with AddHistoryStr() is going to take in the order of half an hour.

I therefore contemplate hacking the history buffer directly.

My question is, will this corrupt TSE's functionality?
In other words, does TSE maintain meta data for its history buffer?
For example,
- does TSE also maintain an index to the history lists,
- or does NumHistoryItems() circumvent recounting list entries in the historybuffer?

Carlo

[Knud van Eeden]

FYIO:

Filling all 127 history entries with 65535 entries takes about 1 minute here in TSE for Microsoft Windows version 4.50.19

Thus not 30 minutes.

PROC Main()
 STRING s[255] = "Test"
 INTEGER I = 0
 INTEGER minI = 1
 INTEGER maxI = 127
 STRING s1[255] = ""
 STRING s2[255] = ""
 s1 = GetTimeStr()
 Message( s1 )
 FOR I = minI TO maxI
  DO 65535 TIMES
   AddHistoryStr( s, I )
  ENDDO
 Message( I )
 IF WaitForKeyPressed( 0 ) ENDIF // Activate if using a loop
 ENDFOR
 s2 = GetTimeStr()
 Warn( "Time used", ":", " ", "from", ":", " ", s1, " ", "to", " ", s2 )
END

with friendly greetings

Knud van Eedne

--

---
You received this message because you are subscribed to the Google Groups "SemWare TSE Pro text editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to semware+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/semware/004301dca0dc%24554cfb70%24ffe6f250%24%40ecarlo.nl.

[Knud van Eeden]

FYIO:

Further if this question would have been asked in professional environments then there the feedback would have been that

hacking into the inner workings of a product by users has usually side effects.

Typically that it is not supported by the support and development, as it circumvents the usual certified and official external entries to the inner working of the product.

Typical side effects are that it might be working in a current version of the product, but not anymore in a future version

because those used by the user specific internal workings of the product might have been changed by the developer.

So it is the responsibility of the user to re-adapt it again at his end, with no support.

It might be working but no guarantee at all thus by the vendor.

But here as the action here should probably be only READING the history (=one of the buffers in memory, that is the 'history buffer') (and not writing to it assumed) it should

be save to fit it to one's purposes is assumed.

with friendly greetings

Knud van Eeden

IT specialist

Further 

[Carlo Hogeveen]

Sorry Sammy,

I hate when I do this.
After using my own brain I found the answer to my question: No.
Hopefully I wasted none of your time.

Carlo

[Fred H Olson]

I find the history feature often handy. I have pondered the problem of
when I have two TSE instances of losing the history from the first
one closed.

I usually have a "main" TSE instance and sometimes a "secondary" less
used instance in another terminal tab. The secondary instance may
just be to look up help so I can leave it open while using the help with
the primary instance. Usually the second instance is less used and
results in less history. I try to remember to close the primary
instance last but often fail to remember.

A way to force closing the primary instance last would be a big step to
reducing the problem.

Fred

--
Fred H. Olson Minneapolis,MN 55411 USA (near north Mpls)
Email: fholson at cohousing.org 612-588-9532
My Link Pg: http://fholson.cohousing.org ybb_

[Knud van Eeden]

That request seems to ask just for algorithms writing all the Histories from all TSE sessions running to e.g. totally 127 file(s) 

and then merging and cleaning (=keep unique one) and then reloading those files again at startup.

with friendly greetings

Knud van Eeden

Here example of getting the history:

--

---
You received this message because you are subscribed to the Google Groups "SemWare TSE Pro text editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to semware+u...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/semware/f8ad4dc3-8e4f-65e4-57c1-5b2f8f64c61d%40cohousing.org.