Project

General

Profile

Bug #2799

Bug #2677: fix drawing and functional differences between P2J GUI and 4GL GUI

browse widget doesn't execute validation expressions in P2J (both chui and gui)

Added by Greg Shah over 8 years ago. Updated over 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:

upbrowse.p Magnifier (410 Bytes) Igor Skornyakov, 11/01/2015 10:57 AM

Related issues

Related to User Interface - Feature #2564: implement GUI BROWSE widget Closed
Related to User Interface - Feature #1801: add some frame options Closed 02/22/2013 08/16/2013
Related to User Interface - Feature #3275: improve browse support Closed

History

#1 Updated by Greg Shah over 8 years ago

#2 Updated by Igor Skornyakov over 8 years ago

The NO-HELP/NO-VALIDATE/NO-AUTO-VALIDATE options behavior for the BROWSE widget is as described below (see attached program).

1. Explicit HELP/VALIDATE options override a schema-defined ones
2. FRAME:NO-HELP option doesn't suppress help message for the BROWSE widgets.
3. FRAME:NO-VALIDATE option doesn't suppress neither explicit not the schema-defined validation for the BROWSE widgets.
4. BROWSE:NO-VALIDATE option suppresses schema-defined validation bot not the explicit one.
5. Both FRAME-NO-AUTO-VALIDATE and BROWSE:NO-AUTO-VALIDATE suppress automatic validation (explicit and scheme-defined).

#3 Updated by Igor Skornyakov over 8 years ago

BTW: There is no NO-HELP option for the BROWSE widgets in the Progress documentation. However 4GL doesn't complain if it is provided, just silently ignores it.

#4 Updated by Greg Shah over 8 years ago

Good results.

Both FRAME-NO-AUTO-VALIDATE and BROWSE:NO-AUTO-VALIDATE suppress automatic validation (explicit and scheme-defined).

Which of the following is true?

1. If either FRAME:NO-AUTO-VALIDATE OR BROWSE:NO-AUTO-VALIDATE is set, then automatic validation will be suppressed.

2. Automatic validation is only suppressed if BOTH FRAME:NO-AUTO-VALIDATE AND BROWSE:NO-AUTO-VALIDATE are set.

#5 Updated by Greg Shah over 8 years ago

How does the browse validation get invoked using the VALIDATE() method and the VALIDATE language statement?

#6 Updated by Igor Skornyakov over 8 years ago

Greg Shah wrote:

Good results.

Both FRAME-NO-AUTO-VALIDATE and BROWSE:NO-AUTO-VALIDATE suppress automatic validation (explicit and scheme-defined).

Which of the following is true?

1. If either FRAME:NO-AUTO-VALIDATE OR BROWSE:NO-AUTO-VALIDATE is set, then automatic validation will be suppressed.

2. Automatic validation is only suppressed if BOTH FRAME:NO-AUTO-VALIDATE AND BROWSE:NO-AUTO-VALIDATE are set.

The first one is true.

#7 Updated by Igor Skornyakov over 8 years ago

Greg Shah wrote:

How does the browse validation get invoked using the VALIDATE() method and the VALIDATE language statement?

I haven't checked this yet. I will do this later.

#8 Updated by Greg Shah over 8 years ago

Actually, ignore the VALIDATE language statement case. We are pretty sure this has nothing to do with UI features. It is about validating the pending database record changes.

But it is important to check the validate() method for frame to confirm it handles the contained browse.

#9 Updated by Igor Skornyakov over 8 years ago

Greg Shah wrote:

Actually, ignore the VALIDATE language statement case. We are pretty sure this has nothing to do with UI features. It is about validating the pending database record changes.

But it is important to check the validate() method for frame to confirm it handles the contained browse.

I see, thank you. I also have an impression that the VALIDATE statement is not related to UI.

#10 Updated by Greg Shah about 8 years ago

  • Target version deleted (Milestone 12)

The customer reports that this is unlikely to be used currently, but it is not known for sure one way or the other. Even if it is needed, the customer is willing to defer this until later.

We have agreed that this will be put on hold and we will implement it if and when the customer informs us that it is required.

#11 Updated by Greg Shah almost 7 years ago

#12 Updated by Greg Shah over 6 years ago

Can this be closed?

#13 Updated by Stanislav Lomany over 6 years ago

FRAME:NO-AUTO-VALIDATE option is mentioned here and I didn't deal with it. Otherwise it can be closed.

#14 Updated by Greg Shah over 6 years ago

FRAME:NO-AUTO-VALIDATE option is mentioned here and I didn't deal with it. Otherwise it can be closed.

I believe that the FRAME:NO-AUTO-VALIDATE option is already fully supported. Constantin: is there anything missing that you know about?

And now the BROWSE version is also fully supported, right? The option in rules/gaps/user_interface.rules is still marked partial because of browse. I think it wasn't updated with all recent changes.

#15 Updated by Stanislav Lomany over 6 years ago

And now the BROWSE version is also fully supported, right?

Right.

#16 Updated by Greg Shah over 6 years ago

Stanislav Lomany wrote:

And now the BROWSE version is also fully supported, right?

Right.

Please update the gap analysis rules in one of your existing task branches.

Also available in: Atom PDF