Allen,
It's been my experience that more events fire in v15 forms than fired in older
versions. I started turning off as many unneeded events in converted forms as
possible, and surrounding code with a test for the desired event. Sometimes
the test will include a flag.
It's mostly a clean up of (or working around) loose habits from 4Ds more
accommodating days.
Case of
: (Form event=On Display Detail) & (OKToUseODDFlag)
OKToUseODD:=False
....
End case
Keith - CDI
> On Feb 7, 2017, at 1:47 PM, Allen Matlick <[email protected]> wrote:
>
> Hi,
>
> We have a database that we’re trying to transition from v13 to v15. It
> originally began in v3.5 and has been updated as 4D has advanced.
>
> We have some detail forms which have variable fields where information is
> entered that is used for queries and a subform which displays the query
> results..
>
> The list form that is attached to the subform area has code which executes
> each time an ‘on display detail’ event occurs.
>
> In v13 we could type some info into one of the variable fields and then tab
> out to execute the query and the displayed records would execute the ‘on
> display detail’ event once for each of the displayed records. With v15 we
> are finding that the ‘on display detail’ events are being generated many,
> many more times than they were with v15. In this specific case, each time a
> letter is typed into the entry variable the displayed info refreshes. Net
> effect is a very, very sluggish user interface.
>
> In one case, the display detail events are being triggered so frequently that
> the form is barely usable. We have restricted the activated events for the
> forms to the minimum we can. We are also seeing some things which are
> confusing, e.g. each time we type a character into a data entry variable the
> entire form redraws, but if we turn off the ‘on clicked’ event then the
> redraws stop.
>
> It seems that form events are propagating very differently in v15 compared to
> v13. Can anyone provide any insight, pointers to docs, … ?
>
> We’re using a subform for display because we want to display 2 lines of data
> for each record and in some cases we include graphic elements which behave
> like buttons so that the user can bring up more info about specific
> components of the displayed information.
>
> Any insight would be appreciated. Thanks.
>
> Allen
>
>
> **********************************************************************
> 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]
**********************************************************************
