Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!rutgers!bellcore!att!chinet!saj
From: saj@chinet.chi.il.us (Stephen Jacobs)
Newsgroups: comp.sys.atari.st
Subject: Re: Designing HIs under GEM
Summary: The Mark Williams rcs has occasional problems
Message-ID: <9418@chinet.chi.il.us>
Date: 30 Aug 89 04:34:58 GMT
References: <11830048@hpldola.HP.COM> <11830050@hpldola.HP.COM>
Organization: Chinet - Chicago, Ill.
Lines: 22

In article <11830050@hpldola.HP.COM>, jg@hpldola.HP.COM (Joe Gilray) writes:
> 
> About the 255 editable (FTEXT or FBPOXTEXT) character limit per box that
> I mentioned earlier, I am using MWC (v3.0.6), the MW resource constructor,
> and original ROM TOS (v1.0?).  Am I the only one who has noticed this?
> What might I be doing wrong?  Any suggestions as to how I might test to
> be sure this is the problem?
>
I constructed a resource file with about 10 trees and a lot of editable fields
within dialogs using resource.prg.  It gave some funny behavior.  When
decompiled with the utility provided by Mark Williams Company, it had some
obvious errors, and an attempt to compile the decompiled file crashed my
ST.  The people at Mark Williams Company have identified the problem (although
they didn't seem anxious to tell me what it was: I suspect it involves the
cavalier treatment of default text, validation strings and templates).  They
tell me it took some unusual bad luck to activate it, and that it will be fixed
in the next release.  Until then, whenever a resource constructed with the
Mark Williams resource construction program behaves strangely, it's probably
a good idea to look at what it decompiles to.  Look particularly for trees
with duplicate (and incorrect) names >in the decompilation<.
                                Steve J.