Skip to main content

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



------------------------------
Ingo Stiller
Aareon Deutschland GmbH
------------------------------

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



------------------------------
Ingo Stiller
Aareon Deutschland GmbH
------------------------------

I agree with A. 

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

Regards, 

Iain



------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------

I agree with A. 

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

Regards, 

Iain



------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------

Hi Iain


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

Ingo



------------------------------
Ingo Stiller
Aareon Deutschland GmbH
------------------------------

Hi Iain


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

Ingo



------------------------------
Ingo Stiller
Aareon Deutschland GmbH
------------------------------

about B: right mouse button too, but double click is better .

Right button on an entity also opens the model definition.

IMO, v10 takes a bit of getting used to, but it is an improvement.



------------------------------
Osman Shariff
------------------------------

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



------------------------------
Ingo Stiller
Aareon Deutschland GmbH
------------------------------

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



------------------------------
Norbert Lauterbach
Infraserv Gmbh & Co. Höchst Kg
Frankfurt DE
------------------------------

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



------------------------------
Norbert Lauterbach
Infraserv Gmbh & Co. Höchst Kg
Frankfurt DE
------------------------------

Hi Nobert 

If you have time, you can go through our code and check 78847 *) entries to see if that should be replaced by "function" :-)
( * Just search for "ENTRY" in all script containers )

Ingo



------------------------------
Ingo Stiller
Aareon Deutschland GmbH
------------------------------

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



------------------------------
Norbert Lauterbach
Infraserv Gmbh & Co. Höchst Kg
Frankfurt DE
------------------------------

I have added the "function" statement to my prettifier 

Here is an example what the prettifier does with such kind of statements 
Before:

As you can see , there three problems

  1. The 'end'  for 'entry" is missing
  2. There is an extra 'end'
  3. A string is not closed

Here is the result

After all 'end' a comment with the name of the procedure will be written (if not already a comment exists)

At least two line between 'end' and the next statement

Extra 'end's a marked inline as they may change the ident

remarks in an extra output window

The prettifier can handle other proccode-statements with indent as well precode directives.
GOTO-Tags are indent only the half 
I can switch between ident by a number of chars or tabs ("online", without leaving the program)

BTW:
Internally, the prettifier parses the whole proccode and build a 'tree' structure with tokens
Okay, only the tokens I need tor prettify :-)
And it is not a real tree as the pretfifier is very old, there was no tree in UnifAce at that time

Ingo

xxxx



------------------------------
Ingo Stiller
Aareon Deutschland GmbH
------------------------------

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



------------------------------
Ingo Stiller
Aareon Deutschland GmbH
------------------------------

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
------------------------------


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
------------------------------

Ooh, learn something new every day... 

Is there a "Using the IDE" video somewhere? 

Regards, 

Iain



------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------