O7 -> O$ prompted find

Hi Paul,

Which events are triggering the validation code?

We try to stay away from adding validation code behind fields so that
users don’t get stuck while entering data. Instead we have a
$checkInsertEdit() method that is called when the user saves the data.

That said, an instance var to determine what type of input you expect is
not a bad idea. We defined a short integer in our super window:
1=insert, 2=edit, 3=find.

Best regards,

Nick Renders

On 14 Mar 2018, at 8:22, Paul Mulroney wrote:

> Hi Everyone,
>
> I’m converting an Omnis 7 app to Omnis Studio. I’ve discovered that if
> you have a “prompted find”, in Studio you get events now, whereas in
> Omnis 7 during prompted find you didn’t. This is causing some grief
> because all the validation code is complaining about fields missing
> values etc.
>
> Is there an easy way to say “during prompted find, don’t execute any
> events”? Can I even tell if I’m in prompted find mode using a
> built-in property or method? At the moment I’m resigned to setting an
> instance var that says “Hey, I’m in find mode”, and in every $event
> having a “if I’m not in Find mode…”. Some of these windows have a
> few fields…
>
> Regards,
> Paul.
>
>
>
> Q: What’s the best thing about elevator jokes?
> A: They work on so many levels.
> —
> Paul W. Mulroney We Don’t
> Do Simple Pty Ltd
> pmulroney@logicaldevelopments.com.au Trading as Logical
> Developments
> www.logicaldevelopments.com.au ACN 161 009 374
> Ph: +61 8 9458 3889 86
> Coolgardie Street
> BENTLEY
> WA 6102
>
>
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en@lists.omnis-dev.com
_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com
Start a new message -> mailto:omnisdev-en@lists.omnis-dev.com