Project

General

Profile

Bug #9492

interactive and redirected widget registry is mixed up while redirect mode active

Added by Andrei Iacob over 1 year ago. Updated 9 months ago.

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

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
15626
version_resolved:
reviewer:
production:
No
env_name:
topics:

testcase_9492.p Magnifier (866 Bytes) Andrei Iacob, 12/20/2024 04:06 AM

History

#1 Updated by Andrei Iacob over 1 year ago

  • version_reported set to 15626
  • Assignee set to Andrei Iacob
  • File testcase_9492.pMagnifier added

In the current revision of FWD (15625), widget registry used by the client is determined if interactive/redirected mode is used. Based on this information, widget registry contain different implementation for the same abstract widget defined.

Defining the widgets is not affected by the mode active, because the registry of them is done in force-interactive mode, following that if the previous mode was redirected, widgets that are implementation of StreamableWidget to be created and added to the redirected registry (only a handful of widgets actually implement this interface).

Issues affects any attribute set done during redirected mode, because all retrieves of widgets on the client side are done to the redirected registry, which actually may not contain our widget, and no configuration and related processing is done. Even though output is redirected, we can still have the widget drawn to the default output using instruction ENABLE, but any config changes done outside the define phase will not be reflected.

Testcase is attached. Compared to how OE draws the dialog-box, FWD missed the screen-value, non computed num-lines attribute and any attributes related the widget size.

#3 Updated by Andrei Iacob 9 months ago

  • Assignee deleted (Andrei Iacob)

Also available in: Atom PDF