Quick Commander v4.00 (preview)
ZXNet echo conference «zxnet.soft»
Hello, Witch Doctor
Oh, by the way, there will be a normal viewer of texts - with tabs, with any option
line feed and changeable encoding? =)
Hello, lvd
I highlighted what concerns QC 4.00 in a separate topic.
2lvd: there will be tabs, but in version 4.01. For version 4.00 changes and so on
too much. In the viewer, first of all, I want to add search, and then tabs.
Everything else that you listed is in QC v3.10.
In QC4.00beta8 the viewer has already undergone the following changes:
[!] viewing Alasm sources! The source is colored in different colors in
depending on the operators.
[+] Added a third Mode: the text is black and white, color symbols are replaced with
spaces.
[-] bug with lines longer than 256 characters
[-] bug with Mode=b/w if you load a file and turn on colors
[-] bug when exiting the viewer SP=SP-2
And of course, background music playback, viewing packaged texts
up to 184 sectors long (from 128).
Hello, Witch Doctor
> To what extent is this beta working?
In principle, I debugged everything that is in it. When I teach basic to run, it will be
full beta.
Hello Specter
To what extent is this beta working?
Hello Specter
Thank God, the process is underway... I was afraid that it was all over :) Specter is mired in
life... But no!
Hello Specter
Spe> Yesterday I sat for a day and added tab support (after request
Spe> LVD) into the viewer, which eliminated the second major drawback of the new
Spe> viewer. For QC v4.00 I think I won’t touch the viewer anymore.
Wow, this is going to be the coolest viewer! Now I will look exclusively at the texts
speck, not on PC and not on Amiga!
(modestly so) is it possible to enter ones that are just #0a too? ;)
Hello Specter
Spe> I recently took up the task of eradicating the biggest drawback of the new
Spe> viewer (the one in QC v3.10) - this is an unpleasant delay after loading
Spe> file before text output begins (up to 4 seconds on large files).
Spe> This is due to the fact that at this moment a table of strings is being built (for
Spe> of subsequent fast scrolling), the text encoding is determined
Spe> font is generated. The slowest generation procedure here
Spe> lines, which I tried to speed up by unwinding
Spe> cycles and transitions, replacing JR with JP. We managed to speed it up by 1.5-2 times and
Spe> is the limit for such a procedure. However, the delay is still the same
Spe> remained pretty decent. The second victim was the procedure
Spe> encoding definitions, now even if the file is 65535 bytes long,
Spe> definition works only for the first 16384, which is quite enough.
Spe> But later the “flash” dawned on me :), and I did the following trick:
Spe> after loading the file, build a table for the first 23 rows and display themSpe> on the screen, and in the meantime the user thinks what kind of file he opened and looks
Spe> to the first screen, we are slowly building a table of all lines of text.
Spe> Thus, the victory of the human mind over the stupid machine is achieved.
Spe> ;)
Spe>
Spe> Yesterday I sat for a day and added tab support (after request
Spe> LVD) into the viewer, which eliminated the second major drawback of the new
Spe> viewer. For QC v4.00 I think I won’t touch the viewer anymore.
Well, good luck and free time. And we all have patience while waiting for the new one
versions.
Hello Specter
I recently set out to eradicate the biggest drawback of the new viewer (that
that in QC v3.10) is an unpleasant delay after loading the file before starting
text output (up to 4 seconds on small files). This is due to the fact that in this
moment a table of rows is built (for subsequent fast scrolling), determined
text encoding, font is generated. The slowest procedure here
generating strings, which I tried to speed up by unwinding
cycles and transitions, replacing JR with JP. We managed to speed it up by 1.5-2 times and this is the limit
for such a procedure. However, the delay still remained quite
decent. The second victim was the encoding determination procedure, now even
if the file is 65535 bytes long, the definition only works for the first 16384, which
quite enough. But later a “flash” dawned on me :), and I did the following
trick: after loading the file, build a table for the first 23 lines, display them on
screen, and while the user thinks what kind of file he opened and looks at the first one
screen, we are slowly building a table of all lines of text. Thus
The victory of the human mind over the stupid machine has been achieved. ;)
Yesterday I sat for a day and screwed up tab support (after LVD’s request) in
viewer, which eliminated the second major drawback of the new viewer. For QC v4.00
I think I won’t touch the viewer anymore.
Hello, lvd
Here! Specter once again proved and showed that the programmer is not honest at all
a man, but a smart-ass elk, forced to fool not only the user but also the piece of hardware.
Only politicians, and only big ones, are more resourceful than programmers.
Yes! Enter simply by 0a too!
Hello Specter
Spe> So, back in QC v3.10, the viewer understood line separators and #0d and #0a
Spe> and #0d0a. Read the help to it.
I'm glitching then. I just remember when I loaded #0a into some qc with enters, and it
showed bullshit =)
Hello, lvd
lvd> (modestly so) is it possible to enter just #0a too? ;)
So, back in QC v3.10, the viewer understood line separators and #0d and #0a and #0d0a.
Read the help to it.