🚀 go-pugleaf

I Bugs in MMRCP and RCS
Since UniTerm (my terminal program) now loads its own keyboard table, I decided
to write a fullscreen keyboardtable editor three days ago. My original idea
was to have a dialog box with all keys and the complete character set as
objects in it (about 350 objects). I started creating the RSC file with the
version of the MegaMax resource construction program included in TDI's
Modula II toolkit, all went well till I had about 200 objects (and I can tell
you that is a lot of work!) then  MMRCP started bombing on me when I tried
to save the resource, possibly there is some connection with naming so many
objects since I was able to load and save the file without the .DFN file.
The next thing I tried was to load it in to DR's RCS (renaming the extension
to of the definition file to .DEF), this worked so I finshed  naming the
objects  then I tried to save the file. RCS didn't bomb on me but it didn't
create a proper output file, so I loaded the resource file in again without
the .DEF file and after naming all the objects again I was able to save it
ok. The next problem was that the maximum size of a dialog box in RCS is
smaller than in MMRCP and I had two buttons which I couldn't select or move
just at the bottom of the dialog box. I tried to cut and paste the two boxes
with the keys and characters to a second dialog box this worked but somehow
messed up the structure of the resource file, its been impossible to name
some of the objects since then....

Before I start building the resource file again, does anybody know what the
limits of RCS are?

II A list of bugs!?
What about somebody starting a list of bugs in commercial products (including
TOS and GEM)? This would save a lot of people a lot of trouble since you
could inform yourself about problems, limitations etc, before you started
a project (or even before you bought the program). Maybe this could even
motivate some firms to get off the list.

                      Simon Poole
                      K538915@CZHRZU1A.BITNET

P.S. Now you know why UniTerm 1.3 is so late!