fmLogAnalyser: TargetObject(s) and TargetType(s) for fmIDE integration
mrwatson-de opened this issue · 0 comments
mrwatson-de commented
Currently fmLogAnalyser analyses the log text relatively simply, which means that in certain (important) log lines fmLogAnalyser is not able to identify the object correctly, and thus will not be able to go to the necessary point in the FileMaker IDE.
The following examples show the complexity of where the info about a target object must come from:
Filename / Object | Message / Text | Import-Type | Phase | TargetType | TargetObject |
---|---|---|---|---|---|
Install Menus::13::Install Menu Set (1) | Menu set “UserMenu” missing. | scripts | 3 | script_name | "Install** Menus" must come from Object1 |
Start script::9::Set Variable | Function referred to in the calculation “M_PfadverwaltungVerwendungErmitteln(Get(ScriptName))” is missing. | scripts or script steps | 3 | script_name + script_step_number | "Start script" from Object1, "9" from Object2 |
MyFile.fmp12 | Function “M_EM_GetHeader” imported as “M_EM_GetHeader 2” since a function named “M_EM_GetHeader” already exists. | custom funtions | 3 | custom_function_name | TargetObject: “M_EM_GetHeader 2” from Text (2) |
(1) Format = {{script_name}}::{{script_step_number}}::{{script_step_command_name}}
(2) Note: Where objects are renamed, the source-name is different from the target name, Source-Name: “M_EM_GetHeader”
This needs to be displayed better and make the "fmIDE Go to" button possible.