Uniface on GitHub
Product (releases and patches)
Fixes and Updates
Im always try to group/cluster code.The LPME (Local procscript for entities) is a perfect place to do so.
But with UnifAce 10, the tree of "modules" on the right side don't show anymore ENTRYsIngo
I think the issue you are reporting is that (as in the example below) the list on the right only shows the triggers for the object - after resolving the inheritance/include scripts - and not the entries defined in the script container.
If you wish to use this window to find an entry, you need to look at the component level where they are all listed. In version 9 we had to either look into the proc listings or go hunting for them in any number of locations.
If you wish to find a trigger, operation or entry within a known container - even if it is not destined to win the inheritance race - you need to use the module inspector available from the tree.
Let me know if you are looking for something else.
The window on the right side of the script editor contains the Compiled Module Information (CMI) - the modules compiled into the component after all inheritance and overriding have taken place. Local proc module are found at the component level as their names are unique within the component. Double-clicking the entry in the CMI window will navigate you to where it was defined.
If you would like to find a module within a specific container, you can use a window that is accessible by hovering over the field/entity/component entry in the tree to the left of the code window and click on the arrow that appears.
In patch 007 the entity editor will also use the Uniface 10 standard editor.
With write script selected a left click on the down arrow on the structure editor will show all these entries.
BTW:Thinking about the problem, I recognize, that you already could jump into any point into the source (not int CMI)When there are warnings/errors when compiling, there is a link to the exact position.So why not use this mechanism?At compiling, store for every "modul" a link of this kind into CMI.Ingo
"If you would like to find a module within a specific container, you can use a window that is accessible by hovering over the field/entity/component entry in the tree to the left of the code window and click on the arrow that appears."
Okay, but if I double click, nothing happens.And I believe I know the answer As one mentioned before, the lookup for proc script only works with CMI (Compiled Module Information)But this is not what a programmer need.We need somthing to jump to the definition of proc script, not the compiled version.
So please change this behaviour!A solution is to include the source-position when compiling the proc to CMI.Later UnifAce can fetch this information and jump to the position in proc script.Simple and would improve the editor.
BTW: In the real world, there are not only "formular one race tracks" but a "little bigger" appllications written
The "problem" is, that I see in right list the entries after compiling.What I expect are those entries, that are defined in this script in the middle.I is a "nice to have" to see technical details after comiling, but for writing script, the actual written things are more importend.
e.g in C++ you don't see the function names after name mangeling but before as the are writeIngo
That may be right (only compiled things are show on right site)
But I don't want to see, what is there after compiling, but what the source code look like.And I dont' want to see operation on rigtht but modules on left site.
Either you give as real classes (like C++) or you have to show the source code.This is due the fact, that there are sometimes a "few" modules, which have to group and not all in one big procscript container.
© 2019 Uniface Privacy & Cookies | Privacy Statement | Legal