VOGONS


TEDIT v0.60 [MULTI-DOC SUPPORT]

Topic actions

Reply 80 of 89, by cookertron

User metadata
Rank Member
Rank
Member

Version 0.60 released - github.com/cookertron/TEDIT

  • Multi-document support (up to 8 ) - shortcut keys ALT+<n> to select
  • Document selection side panel accessible via F1
  • Projects added to support opening multiple documents
  • Shell to DOS added in the File menu - in combination SHROOM (see igully's post above) can free up memory if tight
  • Added missing keyboard shortcuts
  • File selection dialog issues patched
  • Various other bugs (see changelog)

Please give it a whirl and let me know your thoughts.

Asus P5A v1.06, Gigabyte GA-6BXDS, Soyo SY-5EMA (faulty), Viglen 486, Asus SP97-V

Reply 81 of 89, by Yoghoo

User metadata
Rank Oldbie
Rank
Oldbie

Very busy atm so only did a very quick test. Multi-doc edit works nicely. Thanks. Some issues:

  • Starting editor like: tedit 1.txt 2.txt only opens the first file. It should open all files given on the command line (until max of course).
  • Starting editor like: tedit test.prj opens this file but I expected it would open the files in the project. Opening the project inside the editor works fine btw.
  • Quiting TEDIT and just pressing Y or N does not do anything (as a shortcut)

Reply 82 of 89, by igully

User metadata
Rank Member
Rank
Member

Just gave a quick test to v0.60.

Nothing to say, but thank you!

Reply 83 of 89, by aVd

User metadata
Rank Member
Rank
Member

Hi, guys,
I quickly compiled the new multi-file TEDIT version 0.60.0 from the source (I only change default TABs value to 4 and one string as reminder, that this is a customized version) and tested it in DOSBox. I was skeptical about the multi-file edit option, but it seems to work fine 😀

One buggy thing, that I noticed in DOSBox (and DOSBox-X as well), is related to the new DOS prompt option: after return from DOS prompt back into TEDIT, the mouse stops responding and the mouse cursor disappears. Still I haven't tested latest TEDIT version on a real hardware, so I'm not sure if this problem appears only in DOSBox and DOSBox-X emulators.

I can't get how to use SHROOM with software products supporting start of a new DOS command interpreter instance. Probably Ignacio could give a brief explanation.

Thank you!

DOS fan :: artificial "intelligence" (chat) bots - not a fan... not a fan at all :: is freeware a lie, when human freedom is a fundamental lie?

Reply 84 of 89, by cookertron

User metadata
Rank Member
Rank
Member
aVd wrote on Today, 10:47:
Hi, guys, I quickly compiled the new multi-file TEDIT version 0.60.0 from the source (I only change default TABs value to 4 and […]
Show full quote

Hi, guys,
I quickly compiled the new multi-file TEDIT version 0.60.0 from the source (I only change default TABs value to 4 and one string as reminder, that this is a customized version) and tested it in DOSBox. I was skeptical about the multi-file edit option, but it seems to work fine 😀

One buggy thing, that I noticed in DOSBox (and DOSBox-X as well), is related to the new DOS prompt option: after return from DOS prompt into TEDIT, the mouse stops responding and the mouse cursor disappears. Still I haven't tested latest TEDIT version on a real hardware, so I'm not sure if this problem appears only in DOSBox and DOSBox-X emulators.

I can't get how to use SHROOM with software products supporting start of a new DOS command interpreter instance. Probably Ignacio could give a brief explanation.

Thank you!

I can replicate that bug and will look into it. As well as the mouse disappearing the hardware cursor appears in the top left corner too. It maybe that everything needs to be re-initialised after exiting from DOS.

I've not tried it myself but to use SHROOM you use it like this "SHROOM TEDIT <filename.txt>"

Yoghoo wrote on Yesterday, 21:09:
Very busy atm so only did a very quick test. Multi-doc edit works nicely. Thanks. Some issues: […]
Show full quote

Very busy atm so only did a very quick test. Multi-doc edit works nicely. Thanks. Some issues:

  • Starting editor like: tedit 1.txt 2.txt only opens the first file. It should open all files given on the command line (until max of course).
  • Starting editor like: tedit test.prj opens this file but I expected it would open the files in the project. Opening the project inside the editor works fine btw.
  • Quiting TEDIT and just pressing Y or N does not do anything (as a shortcut)

Thanks for the heads up. I'm looking into extending TEDIT's command-line arguments.

Asus P5A v1.06, Gigabyte GA-6BXDS, Soyo SY-5EMA (faulty), Viglen 486, Asus SP97-V

Reply 85 of 89, by aVd

User metadata
Rank Member
Rank
Member
cookertron wrote on Today, 15:14:

I can replicate that bug and will look into it. As well as the mouse disappearing the hardware cursor appears in the top left corner too. It maybe that everything needs to be re-initialised after exiting from DOS.

I've not tried it myself but to use SHROOM you use it like this "SHROOM TEDIT <filename.txt>"

Hi, @cookertron,
I thought, that the mouse is also reinitialized (just like the display text mode) after the command interpreter instance is terminated. But probably I'm mislead by quick scrolling through CHANGELOG.MD file.

So, basically SHROOM is something like software wrapper instead of a TSR program. I thought, that I have to put it somehow into CONFIG.SYS 😁 Thanks for the clarification!

P.S. This is a quote from CHANGELOG.MD for the latest TEDIT version 0.60.0:

On return: restores SS:SP, resets video mode 3, reinitializes mouse driver, triggers full TUI screen redraw

Hmm. Seems like the mouse driver reinitialization is not enough for DOSBox and DOSBox-X emulators.

DOS fan :: artificial "intelligence" (chat) bots - not a fan... not a fan at all :: is freeware a lie, when human freedom is a fundamental lie?

Reply 86 of 89, by cookertron

User metadata
Rank Member
Rank
Member
aVd wrote on Today, 15:29:
Hi, @cookertron, I thought, that the mouse is also reinitialized (just like the display text mode) after the command interpreter […]
Show full quote
cookertron wrote on Today, 15:14:

I can replicate that bug and will look into it. As well as the mouse disappearing the hardware cursor appears in the top left corner too. It maybe that everything needs to be re-initialised after exiting from DOS.

I've not tried it myself but to use SHROOM you use it like this "SHROOM TEDIT <filename.txt>"

Hi, @cookertron,
I thought, that the mouse is also reinitialized (just like the display text mode) after the command interpreter instance is terminated. But probably I'm mislead by quick scrolling through CHANGELOG.MD file.

So, basically SHROOM is something like software wrapper instead of a TSR program. I thought, that I have to put it somehow into CONFIG.SYS 😁 Thanks for the clarification!

It is a TSR. Basically it intercept the INT 21h function 4Bh call, dumps the program and allocated memory to a swap file, frees the memory and then executes COMMAND.COM. When the user exits DOS, SHROOM reloads the swap back into memory and jumps back into it. The program is none the wiser.

I'm still looking into the mouse disappearing trick. I'll let you know my findings.

Asus P5A v1.06, Gigabyte GA-6BXDS, Soyo SY-5EMA (faulty), Viglen 486, Asus SP97-V

Reply 87 of 89, by aVd

User metadata
Rank Member
Rank
Member
cookertron wrote on Today, 15:44:

It is a TSR. Basically it intercept the INT 21h function 4Bh call, dumps the program and allocated memory to a swap file, frees the memory and then executes COMMAND.COM. When the user exits DOS, SHROOM reloads the swap back into memory and jumps back into it. The program is none the wiser.

I'm still looking into the mouse disappearing trick. I'll let you know my findings.

I just tested "SHROOM TEDIT" command in DOSBox and it "swaps" about 220KB in a temporary file when command prompt is invoked from within TEDIT, effectively freeing almost the same amount of conventional memory with the new COMMAND.COM instance. But this combination of "SHROOM + software invoking COMMAND.COM" is inconvenient. I don't see how to start SHROOM as a TSR, so there will be no need to type on every TEDIT start "SHROOM TEDIT ...".

Also, @Yoghoo's suggestion for couple of file names (currently up to eight different files) to be opened from command line is valid.

But why only eight opened files with keyboard shortcuts from <Alt> + <1> to <Alt> + <8>? If a swap-file is used for non active opened files, we may have up to ten files opened with ten keyboard shortcuts <Alt> + <1> ... <Alt> + <9> and <Alt> + <0> 😉

And one more final note. <Tab> key is working as expected in dialog boxes (like in file opening dialog box), but <Shift> + <Tab> combo for reversed field switching does not.

DOS fan :: artificial "intelligence" (chat) bots - not a fan... not a fan at all :: is freeware a lie, when human freedom is a fundamental lie?

Reply 88 of 89, by cookertron

User metadata
Rank Member
Rank
Member
aVd wrote on Today, 16:27:

But why only eight opened files with keyboard shortcuts from <Alt> + <1> to <Alt> + <8>? If a swap-file is used for non active opened files, we may have up to ten files opened with ten keyboard shortcuts <Alt> + <1> ... <Alt> + <9> and <Alt> + <0> 😉

TEDIT 0.61 (not released) supports up to 20 files now (see attachment)! However I'm running out of space and need to find ways to reduce the binary size - it's close to 65k which is the limit for a COM file. I could add support to output EXE files in Agent86 but I feel that would spoil the fun. Having said that, adding multi-document args in the command-line will add more bytes, as will SHFT+TAB, as will loading project files from the command-line, as will re-initialising everything after dropping out of DOS (possibly). So things are looking a bit desperate here.

The attachment tedit_009.png is no longer available

Asus P5A v1.06, Gigabyte GA-6BXDS, Soyo SY-5EMA (faulty), Viglen 486, Asus SP97-V

Reply 89 of 89, by aVd

User metadata
Rank Member
Rank
Member
cookertron wrote on Today, 17:25:

TEDIT 0.61 (not released) supports up to 20 files now (see attachment)! However I'm running out of space and need to find ways to reduce the binary size - it's close to 65k which is the limit for a COM file. I could add support to output EXE files in Agent86 but I feel that would spoil the fun. Having said that, adding multi-document args in the command-line will add more bytes, as will SHFT+TAB, as will loading project files from the command-line, as will re-initialising everything after dropping out of DOS (possibly). So things are looking a bit desperate here.

Yep, the 65280 bytes limit for the DOS com-executables is there. I even wonder how you managed to add more new functionalities after the version 0.57.0. Twenty files opened for editing sounds very good, but ten files still seems pretty fine to me.

I don't see any problem, if the new multi-file edit version of TEDIT switch to 16-bit MZ executable format 😉

If you don't mind, I would suggest something. I still like the old single-file edit version 0.57.0 (if I don't mess the numbers). It only lacks the keyboard shortcuts for "Open..." and "Save as...". Please, could you add them and <Shift> + <Tab> combo (in open file dialog box) for the completion of the single-file TEDIT version - let's say version 0.57.1 or why not 1.0, if no more bugs are reported? You could start a brand new feature rich multi-file TEDIT (16-bit DOS exe-file) project with another name - for example MTEDIT from Multi-Text EDITor. Just sharing some thoughts.

Thanks!

DOS fan :: artificial "intelligence" (chat) bots - not a fan... not a fan at all :: is freeware a lie, when human freedom is a fundamental lie?