:<snip>
	:
	:Any ideas what might cause this or workarounds?
	:I've also tried this with my own custom LDEF; it looks like the
LDEF is
	:never sent the _lHiliteMsg message, among other oddities.
	:<end snip>
	:
	:When doing an LDEF make sure that you ALSO have a condition in
your
	:_lDrawMsg otherwise you will miss the hilite.

The problem occurs with the standard system LDEF ID 0 or my custom LDEF.
My custom LDEF has worked fine for years under Systems 6.04-System 8.1.
Since the problem occurs with the standard system LDEF, we can rule out
my LDEF as a source of the problem.  I added the information about my
LDEF because I was able to insert debuggin calls into my LDEF to get
more info about the problem.  One of the symptoms is the _lHiliteMsg is
never sent to the LDEF.

Waverly responded:

Sorry, I'm using 8.1 so I can't try out any LDEF code in 8.5.  I no
longer debug my LDEF's (which I use a lot) using debugger breaks.  Using
the 6 byte code trick from within FB you can even use the debugger to
track down a resolution for your problem.  I gave a full example
complete with documentation at http://www.stazsoftware.com/exdcod.html


Embedded LDEF
                         Bummed out because the latest bug in your LDEF
is literally laughing at your
                         attempts to use MacsBug to track it down?
Wouldn't it be nice to be able to debug
                         your LDEF right in the FutureBASIC II debugger?
Your wish is our command.
                         Many thanks to Waverly Edwards for providing
this really cool example of
                         embedding an LDEF right into your FutureBASIC
source code. Beware LBUGs!



W.