As there is no wish list yet :two small wishes :-)

A)

When you do have proc code on entity/field-level, the sidebar shows only operations/triggers.
Please could also the local procs displayed here.
Yes, they are (also) at componentg level

But there is a reason why the proc code was written at LPME level: Structure and clarity :-)

B)

In UF 9 you could switch between layout => procode and UnifAce  automatically opens the appropriate proc-container
Would be nice to have too in UF 10
Why: Sometimes it is easier to find a field on  the "surface" then in a deep nested structure list

Ingo

I agree with A. 

For B, double click the field on the layout -> Proc Code. 

Regards, 

Iain

Hi Iain

about B: Never tried a double click as this opens the property-window in UF 9  :-)

Ingo

A)

When you do have proc code on entity/field-level, the sidebar shows only operations/triggers.
Please could also the local procs displayed here.
Yes, they are (also) at componentg level

But there is a reason why the proc code was written at LPME level: Structure and clarity :-)

B)

In UF 9 you could switch between layout => procode and UnifAce  automatically opens the appropriate proc-container
Would be nice to have too in UF 10
Why: Sometimes it is easier to find a field on  the "surface" then in a deep nested structure list

Ingo

Hi Ingo,

have you tryed it with the new "Zauberwort" function instead of entry?

You should see the function in the entity or field.

Kind regards

Norbert

Hi Ingo,

have you tryed it with the new "Zauberwort" function instead of entry?

You should see the function in the entity or field.

Kind regards

Norbert

A)

When you do have proc code on entity/field-level, the sidebar shows only operations/triggers.
Please could also the local procs displayed here.
Yes, they are (also) at componentg level

But there is a reason why the proc code was written at LPME level: Structure and clarity :-)

B)

In UF 9 you could switch between layout => procode and UnifAce  automatically opens the appropriate proc-container
Would be nice to have too in UF 10
Why: Sometimes it is easier to find a field on  the "surface" then in a deep nested structure list

Ingo

Hi Ingo,

For A, the CMI shows code being used in the compiled component regardless of where it is defined in the inheritance model. As entries have a component scope, they are shown in the component's CMI. 

If you want to find a module in the current code container, you can use the popup from the component structure.

Kind regards,

Mike

------------------------------
Michael Taylor
Rocket Internal - All Brands
------------------------------