From: Ross_Boyd@tnt.com.au
Thanks for the detailed reply Sammy!
>> Ross Boyd wrote:
>> 1. TSE 2.8 is MUCH slower at responding to keystrokes like CursorUp/Down 
and
>>  PageUp/Down. TSE 2.5 is VERY responsive and fast in this regard. Also,
>Sammy's reply:
>Bottom line is, I do not know what causes it, and I do not know what to do
>about it.  win32 GUI apps do not seem to exhibit this problem, so once we
>release the win32 GUI version of TSE Pro, the problem will be solved for
>many users.
Roll on TSE Pro win32 GUI version.
>> I used a keyboard accelerator (Hyperkey) to really make 2.5 fly.
>> Unfortunately, TSE 2.8 does not get accelerated by this TSR.
>> 
>There is a macro qkeys, that was developed for TSE Pro DOS that does this.
>I have ported it to TSE Pro win32.  I'll post it on our ftp site.  The name
>will be qkeys32.zip.  Should be there by late this afternoon.  It works fine
>for me on my work machine, but I have not tested on my home machine.
Thanks very much! I'll d/l it and give it a try.
>> 2. I am very attached to TSE 2.5's 36-line video mode. Unfortunately,
>> TSE 2.8 won't allow me to go fullscreen when in 36 line mode. That was
>> a real pain. I guess that will be addressed when a TSE for Windows 
is released.
>v2.8 fully supports 36 line mode in a window.  However, win32 
(apparently) limits
>win32 console applications to 25/43/50 lines in full screen mode.  So if you
>want 36 lines (or 55 lines, or 104 columns, or whatever), run v2.8 in a
>window.
Yep, I thought it was a console-mode related problem rather than a TSE 
problem.
>> There is no way around this except to provide a new comment delimiter
>> type with the special attribute that it applies only to BOL
>> comments. In fact I had to make  this very same mod to Ian Campbell's
>> color.asm in TSE 2.5.
> I've added this to my syntax hiliting todo list.
Thanks! Although the RegEx suggestion that someone here made has a lot 
going for it. Speed might be a problem though.
>> I know you hate to talk about what Semware is developing next, but boy
>> I'm curious.
> Our main project is a win32 GUI version.  Side projects that I work on when
> I get stuck with the GUI (there is a pun in there somewhere) are:
>- a 'portable' 32-bit version of v2.8+ (2.9 is the current in-house
>version).  This version currently runs under win32 console, win32 GUI, DOS
>protected mode (e.g., requires a 386/486), and comes up but crashes under
>OS/2.  Not all things work under all versions, for instance, mouse support
>does not work in the DOS32 version, and wouldn't work in the OS/2 version
>even if I could get it to load.  I would eventually like to get this one
>working under linux, both console and x-windows.  But, I have more wishes
t>han I have time, it seems.  As an aside, the DOS32 version works really
>well.  It is a shame we did not do something like this 3 or 4 years ago.  Oh
>well!
It sure is hard to keep up with the pace of technology these days. I 
really feel for you in that regard.  One question though, how does the 
same version run under win32 console AND win32 GUI. I thought it had to 
be one or the other. Or do you mean they're separate builds but mainly 
the same source code?
> All of these versions have undo, with redo still in the works.
Excellent!! I've always thought that undo/redo was the one feature that 
TSE 2.5/2.6/2.8 lacked compared to the competition. That's great news!
Regards,
Ross Boyd

---
---------------