Jacque discovered that the field's autoHilite was set to false. But, then there was some other strange behavior, so there's a bug or two in that sequence. Workaround, of course, is to make a new field and copy the text over.
Thanks, everyone. -- Paul On 4/15/07, Ken Ray <[EMAIL PROTECTED]> wrote:
On Sun, 15 Apr 2007 14:30:44 -0700, Paul Foraker wrote: > Behavior is the same with Focusable true or false, except that with it set > to false, the insertion point doesn't appear at all. Is it possible that you're trapping any of the key messages (keyDown/keyUp, rawKeyDown/up, etc.) in the substack (or later in the hierarchy)? It sounds like the keystroke is being trapped and not passed... Ken Ray Sons of Thunder Software, Inc. Email: [EMAIL PROTECTED] Web Site: http://www.sonsothunder.com/ _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
