[archive] After procedure...

[Migrated content. Thread originally posted on 03 December 2008]

While I prefer to use enable/disable we have some programs coded that are using

modify control-name read-only no-tab.

The issue I'm having is when this is done rather than using enabled 0 the user can click in the field and then click out of the field with a mouse. Doing this causes the after procedure to run which can do things like enable/disable buttons or menu option, change other control values or open other controls up for modification.

Is there anything I can code in the modify to stop the after procedure?

You could inquire on the control to see if it's read only and get out of the after procedure before it executes any code. ?

[Migrated content. Thread originally posted on 03 December 2008]

While I prefer to use enable/disable we have some programs coded that are using

modify control-name read-only no-tab.

The issue I'm having is when this is done rather than using enabled 0 the user can click in the field and then click out of the field with a mouse. Doing this causes the after procedure to run which can do things like enable/disable buttons or menu option, change other control values or open other controls up for modification.

Is there anything I can code in the modify to stop the after procedure?

You could inquire on the control to see if it's read only and get out of the after procedure before it executes any code. ?

[Migrated content. Thread originally posted on 03 December 2008]

While I prefer to use enable/disable we have some programs coded that are using

modify control-name read-only no-tab.

The issue I'm having is when this is done rather than using enabled 0 the user can click in the field and then click out of the field with a mouse. Doing this causes the after procedure to run which can do things like enable/disable buttons or menu option, change other control values or open other controls up for modification.

Is there anything I can code in the modify to stop the after procedure?

I agree, that is one way to handle it but I was hoping for a more "global" method, just like the statement

modify control-name read-only no-tab

is there something I can do like a

modify control-name no-actions
or
modify control-name no-events

Again, I'm hoping to not have to code the inquire for the read-only properties into every after procedure if I can help it.

If I get my way, we'll go to all enabled or disabled anyway.

Thanks for the thought as it may be my best option if there is no other way and we continue to use this method to disable fields.

[Migrated content. Thread originally posted on 03 December 2008]

While I prefer to use enable/disable we have some programs coded that are using

modify control-name read-only no-tab.

The issue I'm having is when this is done rather than using enabled 0 the user can click in the field and then click out of the field with a mouse. Doing this causes the after procedure to run which can do things like enable/disable buttons or menu option, change other control values or open other controls up for modification.

Is there anything I can code in the modify to stop the after procedure?

There is no such thing as you ask for, but you can always have your own flag:

modify control-name read-only no-tab
set my-flag-override to true
...

then in your after procedure>

if my-flag-override is true
   exit section
end-if