Issue 32060 — New field ATTACHED in UFORM not properly implemented in IDE
Status: Planned for resolution in 10.4.01
Solution available in patch(es): 10.3.02.029
Summary: Uniface: New field ATTACHED in UFORM not properly implemented in IDE This causes problems for Non-Modal Detached forms newly created in Uniface 10 This causes problems tab forms that have been migrated to Uniface 10. From the Uniface 10 library: Getting Started > What's New in Uniface 10 > Uniface 10: Repository Changes > Uniface 10: Repository Changes per Entity For UFORM The attach property is moved to ATTACHED ATTACHED is a new field. The new field ATTACHED from UFORM is properly set to F for migrated Non-Modal Detached form and ATTACHED is removed from field WINPROP from UFORM. The Modality & Attachment property is displayed in IDE as Non-Modal Attached where Non-Modal Detached is expected. The new field ATTACHED from UFORM is NOT set for a Non-Modal Detached form created from scratch in Uniface 10. In stead ATTACHED=F is added to the field WINPROP from UFORM. This not in line with the documentation and the compiled form behaves improperly as an attached form: $instanceparent filled , form closes when parent is closed. The Modality & Attachment property is displayed in IDE as Non-Modal Detached as expected. In Uniface 9.7 one can have a modeled form with Window Type normal , Modality & Attachment property Non-Modal Detached. A form used as tab page is derived from this modeled component: Windows Type has been changed to Contained. Now migrate these forms to Uniface 10. After migration the new field ATTACHED is properly set to F for the modeled component. After migration the new field ATTACHED is not set for the derived form used as tabpage. After compiling the derived form used as tabpage behaves as detached because the new field ATTACHED is inherited from the modeled form: $instanceparent not filled This problem occur in Uniface 10. This problem does not occur in Uniface 9.7.
There is no known workaround for this problem.
The 'Attached' component property is now also for Forms, a separate property that can be edited in your Property inspector and is no longer maintained as part of your 'Windows Properties'. This enables the Attached property to inherit correctly from a Modeled component so that the Derived component behaves as expected.