Maxi-/Uber-Edit

Basic and Machine Language

Moderator: Moderators

sjgray
Vic 20 Hobbyist
Posts: 101
Joined: Thu May 03, 2007 6:46 pm
Location: Markham, ON, Canada

Re: Maxi-/Uber-Edit

Postby sjgray » Mon Feb 27, 2017 5:18 pm

Mike wrote:Steve,
In short: this tool is great as wedge, not so as KERNAL patch. A program that uses this tool needs to be fully aware of it anyway. In principle, it gains its merits just like any of the known BASIC extensions - you invest some memory into the wedge to simplify some other aspects in your own code.


As you pointed out, you really are talking of a few programs that would benefit from this, so it really doesn't matter what you break. Luckily BASIC programs will relocate automatically, so that doesn't matter. I think the main benefit of such a program would be simply to have a larger screen to make listing/editing nicer. So, with a kernal switcher you would select this, do your editing etc, save and switch back to normal kernal. If it became a "standard" then perhaps people would develop some specialized software for it. Hard to say. In any case, it's an interesting concept.

Steve

User avatar
Mike
Herr VC
Posts: 2925
Joined: Wed Dec 01, 2004 1:57 pm
Location: Munich, Germany
Occupation: electrical engineer

Re: Maxi-/Uber-Edit

Postby Mike » Mon Feb 27, 2017 5:39 pm

sjgray wrote:[...] you really are talking of a few programs that would benefit from this, [...]

Programs will need to be specially *crafted* for the extended screen, they won't benefit by a happy coincidence.

so it really doesn't matter what you break.

That would be just most other, unaware programs.

I think the main benefit of such a program would be simply to have a larger screen to make listing/editing nicer. So, with a kernal switcher you would select this, do your editing etc, save and switch back to normal kernal.

You make use of a strong premise, namely that people still use the VIC-20 to actually write and edit programs on it. ;)

If it became a "standard" then perhaps people would develop some specialized software for it. Hard to say. In any case, it's an interesting concept.

For me, that is the intended main use of the tool; as wedge, not as KERNAL replacement.

As I wrote in the edit of my preceding post, incorporating this tool into the KERNAL would make its use only easier for the programmer, not for the user. Without the patched screen editor, the client application doesn't work. Loading a wedge into RAM is far easier to do (and much more acceptable for most people) than requiring a hardware change by exchanging the KERNAL ROM.

User avatar
pixel
Vic 20 Nerd
Posts: 867
Joined: Fri Feb 28, 2014 3:56 am
Website: http://hugbox.org/pixel/
Location: various
Occupation: Pan–galactic shaman

Re: Maxi-/Uber-Edit

Postby pixel » Sun Mar 05, 2017 8:19 pm

Oh, dude! What a relief! Same first thought like Boray: .oO( 30 years too late). ;)

BTW: Am using NTSC for a PAL telly and that's already clipping the corners.
A man without talent or ambition is most easily pleased. Others set his path and he is content.
https://github.com/SvenMichaelKlose

User avatar
Mike
Herr VC
Posts: 2925
Joined: Wed Dec 01, 2004 1:57 pm
Location: Munich, Germany
Occupation: electrical engineer

Re: Maxi-/Uber-Edit

Postby Mike » Mon Mar 06, 2017 11:01 am

pixel wrote:BTW: Am using NTSC for a PAL telly and that's already clipping the corners.

That's because the default register values for the horizontal and vertical position are already different for PAL and NTSC. If you program PAL values into an NTSC VIC, the display window is out of center, likewise the other way round. This is of course more severe for overscan display windows.

In principle, the values for these two registers could be derived as (signed) offsets from the default values in the KERNAL ROM. This is for example how MINIGRAFIK (re-)centers the display for its underlying 20x12 (double-height chars) text mode. Obviously tokra didn't do this for Maxi-Edit. ;)

Actually, the 24x26 mode would be quite useful as least common denominator for both TV systems. :)

User avatar
tokra
Vic 20 Nerd
Posts: 799
Joined: Tue Apr 27, 2010 5:32 pm
Location: Germany

Re: Maxi-/Uber-Edit

Postby tokra » Fri Mar 10, 2017 6:50 pm

Following a suggestion by Mike, I amended the source-code, so that is is possible to compile to whatever geometry you like:

Download source

This works with CBM prg Studio. However in Tools-Option-Assembler you need to set the "Operator Precedence (Hi/Lo byte operations) to "Calc address first, then hi/lo byte".

At the start of the source-code you can set if you want to compile for PAL or NTSC. The image is centered accordingly upon compile automatically.

Then you can set the columns and rows. BASIC-line-length is also adjusted automatically, but can be a maximum of 88 characters. So, if for example you choose a mode with just 17 columns, your BASIC-line may use 5 physical line (5*17 =85).

After that you can change the load-address and compile away.

User avatar
tokra
Vic 20 Nerd
Posts: 799
Joined: Tue Apr 27, 2010 5:32 pm
Location: Germany

Re: Maxi-/Uber-Edit

Postby tokra » Sat Jun 17, 2017 4:33 am

I've found a small bug that would strangely only show on real VIC-20. If you pressed STOP/RESTORE the VIC-20 would sometimes crash and sometimes go back to normal display mode. I've cleared up the vector-setup-routine and this seems to fix it. I've updated the files on my webpage to the most recent version (see first post). I also amended the post on how to include MAXIEDIT in your own programs, since the SYS-calls need to go to different addresses now because of the changes.

So please re-download if you are using this.


Return to “Programming”

Who is online

Users browsing this forum: No registered users and 1 guest