On 1 Dec 2017, at 11:28 am, Allan Udy via 4D_Tech <[email protected]> wrote: > >> 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. > > Through a bit of trial and error I can now say with reasonable certainty that > in v16 at least, the plugin Commands now appear to start with 1, rather than > 3 as was necessary in previous versions of your Debug Log Reader. > > A few of the Plugin commands showing up in my Debug Log files take > parameters, and so it's relatively straight forward to match them up with the > actual commands used in the source. It was just a matter of re-parsing the > source Plug-in folder with a different starting ID no each time until the > database then indicates that the Plugin calls are from 4D Internet Commands.
Hi Allan I wish it were always so. I've just generated some logs using v16R5 and the plugins are starting from 3 in them. Maybe it's application-specific. Or maybe it's different for server/client/solo (these were client logs). Anyway, the update I posted to github the other day makes it a little less painful to change the plugin numbers - a right-click lets you renumber them all in one go and you don't need to reparse the logs files to see the changes - just rebuild the hiererchical command list (by holding down the Shift key when selecing them) for any processes you've already examined. cheers J ********************************************************************** 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] **********************************************************************
