calling context...
maybe in the calling context you have/are turning on an event handler
which is still on when the dialog is opened.
as a quick test - insert a bunch of turn offs (on err call ("") on
event call("") etc just before opening the dialog
if it work correctly then work backward removing one of the 'offs'
until it fails again.
On Fri, 12 Aug 2016 12:55:14 -0700, Kirk Brooks wrote:
> Chip,
> On Fri, Aug 12, 2016 at 10:50 AM, Chip Scheide <[email protected]>
> wrote:
>
>> sounds like there maybe an on event call, or on keystroke event running.
>>
>> or are you possibly trying to format the text entry after each key
>> (accidentally)
>>
> I think so too - I'm just having a hard time figuring out where else to
> look. Like I said there aren't any keystroke events enabled for the form or
> any objects on the form. And then - why it happens on this particular
> dialog but not the other one that does essentially the same thing.
>
> Any ideas what I could accidentally enable? I open to suggestions.
>
> --
> Kirk Brooks
> San Francisco, CA
> =======================
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> FAQ: http://lists.4d.com/faqnug.html
> Archive: http://lists.4d.com/archives.html
> Options: http://lists.4d.com/mailman/options/4d_tech
> Unsub: mailto:[email protected]
> **********************************************************************
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive: http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
