That is good news.

My body (and brain) are slowing down too much to attempt big projects any more so I will not be making any big changes to MMEdit.
I will finish aligning the buttons and adding the zoom to MMCC. That will not break anything.

Then I will slowly update the help system.

Jim

Hi Jim
I agree, good job with MMEdit. Is the latest version posted on the website?
/Peter63

  Quote  

Is the latest version posted on the website?

Yes it is up there.
I still have some work to do but it is better than what was there.

Jim

Jim,

Is there any difference between command colouring from 2040 to 2350? 2040 does not support the same set as 2350.
You could automate this by using LIST COMMANDS and LIST FUNCTIONS.

Volhout

P.s. especially usefull for RP2040MIN version, tha has an even smaller subset of MMBASIC.

Might help to use the largest set of keywords, so that programs port more readily across the various MMBasic variants.

John

In the data folder there is a file "kw_list.txt"
It is best viewed in a spreadsheet program that accepts tab separated data.

That is used for the one-line help and entry into the html help.
It is also where i go to to update the syntax colouring files.

A quick look at that file and you will see that I am a long way behind.

My current preference is to keep to a small number of syntax lists and include more rather than less, leaving the user to read the manual.

There may be a good reason for having another syntax file for the RP2040MIN but first I have to get up to date with "kw_list.txt"

Users are free to add their own syntax lists.

Jim

More on increasing the number of device types.

There is a file in the data folder "devicelist.txt"

It is a list of all known MM.DEVICE$ strings (at the time of creating it)
The picomites at that time were:

PicoMite
PicoMite RP2350A
PicoMite RP2350B
PicoMiteHDMI RP2350A
PicoMiteHDMI RP2350B
PicoMiteHDMIUSB RP2350A
PicoMiteHDMIUSB RP2350B
PicoMiteVGA
PicoMiteVGA RP2350A
PicoMiteVGA RP2350B
PicoMiteVGAUSB
PicoMiteVGAUSB RP2350A
PicoMiteVGAUSB RP2350B
WebMite
WebMite RP2350A


Since then, there have been a lot of additions to the list but I have not been able to find where in the firmware these DEVICE$ strings are.
I don't have any way of adding to my list until I find the new device names.

Without knowing the device name, I cannot determine which 'family' the device belongs to.
Without a family, MMCC can't make essential decisions about what commands are safe to use.
The best I can do is assume that if the name contains "picomite" and either "HDMI" or "VGA" it can be treated as "picomiteVGA_HDMI"
otherwise, consider it a bog standard picomite.

I intend to slowly add the new commands to my kw_list.txt and the 3 picomite syntax files.

That will keep me busy for a while.

Jim

I have decided to reduce the number of device choices in MMCC.
Much easier than trying to find a complete list of MM.Device$

I can get away with

I can sort out any differences within a family myself. The fewer choices, the less likely the user will get it wrong.

The flash slots/library commands will get shifted to the main MMCC menu.
That will allow me to tidy the file manager buttons.
It will also allow me to speed up the file manager when it's listing 'mite files.

I won't be able to automatically set the display MODE to a higher resolution so I will give it a button.

MMEdit will keep the same number of syntax files.

Jim

As always Jim, I (and lots of others) really appreciate the effort you put into MMEdit.

I consider it a vital part of my CMM2 experience. I do use the built in editor (of the CMM2) when mucking around - but for really big stuff I use MMEdit.

Thank you.