On Fri, 4 Jun 1999, Alan Pinstein wrote:
> This new error is probably b/c you're reading off the end of a chunk.
> That's why it's rare; it only happens if you read too far. Often happens
> with arrays and reading from either off-by-one array index access or often
> if you use flags such as -1/0xFFFF to mean noSelection then sometimes you
> will read from array[0xffff] which is obvisouly not going to be in your
> allocation block.
>
>
> Alan Pinstein
> Synergy Solutions, Inc.
> http://www.synsolutions.com
> 1-800-210-5293
Well, your argument seems to be right 'cause the second message shows up
BEFORE the contents of the field are written onto screen, although when I
click 'Continue' on POSE warning box the field content is displayed
correctly. The first message showed up with text in field displayed when I
tryed to write something into field by pen.
1)Is there any clever and short way to prevent the second error?
2)How dangerous it really is?
3)I gotta admit that I don't understand how could I read off the end of
the chunk. DmRecord of 256 bytes is attached to a field that can have 20
characters (ok 256 is default testing size). It's all allocated before and
is automatically accessed and writen on screen when form resource
(together with field) is loaded and displayed. Again, how can I prevent
that?
BTW, I checked on POSE 2.1d28 - behaviour is the same as on 2.1d25.
> >I have turned off 'single-line' and the message didn't show up again. The
> >question is why the other message "MyApp read directly from MemMgr data
> >structures" is still here (but very rare - 3 times within 100000
> >gremlin steps).
> >
> >
> >I wonder why such warnings show up so irregulary. Why not *every* time or
> >not at all?
