Hi Justin,
Thanks for that extra info. I'll have to have a play around some more
and try and work out what 4D is actually doing.
ATTENTION 4D: It would be really useful if you would actually publish
the details (somewhere easy to find) of how the DebugLogs determine the
Plugin Command IDs....
Allan
From: Justin Carr<[email protected]>
>
> HI,
>
> A while back I got hold of the v15 '4D Debug Log Reader' database in order to view some of4D's Low Level debugging Log files. It helped me a lot at the time.Does anyone (the author?) know WHY $vL_PluginID is initialised to 3 at the start of the loop through the external plugins....?
That would be me. This was always a tricky piece of the puzzle. Unfortunately there was
no way (that I could find) for determining which plugin was allocated which number in the
debug logs. The best I could determine was that it seemed to load them in alphabetical
order and it usually seemed to start from 3, although not always. I think there used to
be two "plugins" that were built-in to4D - I want to say one of them was the
OLE Tools - not sure what the other one was. I deduced rightly or wrongly that4D was
allocating these numbers first. It's entirely possible that this has changed in more
recent versions.
If it seems to be starting from one now, it would certainly be safe to change
it in the code. You can also change the numbers in the front-end by
double-clicking on them, but the log files would ned to be re-parsed after
you've changed any numbers.
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]
**********************************************************************
