Re: 4D Debug Log Reader - Plugin Commands

2017-11-30 Thread Justin Carr via 4D_Tech
On 1 Dec 2017, at 11:28 am, Allan Udy via 4D_Tech <4d_tech@lists.4d.com> 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

Re: 4D Debug Log Reader - Plugin Commands

2017-11-30 Thread Allan Udy via 4D_Tech
Hi Justin, 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

Re: 4D Debug Log Reader - Plugin Commands

2017-11-29 Thread Justin Carr via 4D_Tech
On 30 Nov 2017, at 10:41 am, Keisuke Miyako via 4D_Tech <4d_tech@lists.4d.com> wrote: > > to clarify: > > - command number > > the command number explained in this example corresponds to the right side of > e.g. "3;1" > and it can be derived from manifest.json inside the plugin bundle (v14