Hi Keisuke,
From: Keisuke Miyako<[email protected]>
the relation between plugin command names and numbers can be studied from
manifest.json (v14 sdk) or *.rsrc (earlier)
https://github.com/4D-JP/plugin-command-numbers
Greatly appreciate you taking the time trying to help, but I really
don't understand your message....
Where/what is '...manifest.json (v14 sdk) or *.rsrc (earlier)...' ?
The issue that Justin Carr and I are discussing is in determining from
the 4D DebugLogs, what plugins are being referred to by the X;YYY
references in the Log file.
In your 'plugin-command-numbers' example database from GitHub, in Method
2 there is the comment:
//in the v14 format (4), the plugin command is printed as 3;10,
//where the first figure is the plugin number
//apparently the index in PLUGIN LIST +2,
//and the second figure is the command number.
Justin previously determined that this is the case, and in his Log
Parsing database that we're using, the plugin command ID's are assumed
to start with 3;YYY.
I'm now trying to examine a Debug Log file generated from a v16R4
database, and there are Plugin References of the form: 2;414
Thus, in v16 (at least), the statement from v14 that '... the index in
PLUGIN LIST +2...' is now INCORRECT.
I'm trying to determine if for v16 it should be that '...the index in
PLUGIN LIST +1...', or indeed if it is something else.
At this stage I'm unsure if the (many many) Plugin calls I'm seeing in
the log (2;414) are being generated by 4D Internet Commands
EX_IS_PROCESS_DYING or not... and whether this is having an effect on
the 4D Remotes being disconnected or not...
When 4D produce a tool as useful as the DebugLog for helping developers
solve very difficult issues, it would be really great if 4D would also
publish all the information required by developers to read these logs
(or better yet provide a good tool to do so). ;-) I would have
thought that a 4D produced (and continually maintained and updated)
DebugLog Parser and Analyser application would not only be of benefit to
developers, but also 4D support staff....
Cheers,
Allan Udy
Golden Micro Solutions Ltd, Blenheim, New Zealand
http://www.golden.co.nz<http://www.golden.co.nz>
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive: http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
