FWD » Core Development » User Interface

Sometimes the frame are not correctly formed. Consider the following procedure:

    define temp-table ttf
       field f  as decimal   init 3.14
       field f1 as integer   init 98
       field f2 as character init 'lups'
       field f3 as logical   init yes.

    define temp-table ttg
       field f  as decimal   init 9.89
       field f1 as integer   init 734
       field f2 as character init 'grem'
       field f3 as logical   init false.

    create ttf.
    create ttg.
    display ttf with side-labels frame f1.
    display skip with side-labels frame f1.
    display ttg with side-labels frame f1.

    buffer-copy ttf to ttg.
    display ttg with side-labels frame f2.

It should print two frames like:

    ┌─────────────────────────────────────────────────┐
    │f: 3.14       f1: 98         f2: lups     f3: yes│
    │f: 9.89       f1: 734        f2: grem     f3: no │
    └─────────────────────────────────────────────────┘
    ┌─────────────────────────────────────────────────┐
    │f: 3.14       f1: 98         f2: lups     f3: yes│
    └─────────────────────────────────────────────────┘

But instead, the display is rather strange:

    ┌─────────────────────────────────────────────────┐
    │f: 734.00     f1: 98         f2: lups     f3: yes│
    │f: 9.89       f2: grem     f3: no                │
    └─────────────────────────────────────────────────┘
    ┌─────────────────────────────────────────────────┐
    │f: 3.14       f1: 98         f2: lups     f3: yes│
    └─────────────────────────────────────────────────┘

Somehow, there is a leakage / naming collision when building the frame at conversion time. The ttg.f1 and ttf.f fields are merged and the output is scrambled.
The annotations/frame_scoping.rules or frame_generator.xml has some flaw that yields two field names that conflict when they should be unique.