LC 8 on Windows

Mike Bonner bonnmike at
Sun Jul 10 11:12:52 EDT 2016

I don't have time to do it today but heres some possible pseudocode for a
tool that would help.

get  revEnvironmentUserPluginsPath() -- the path to the users plugins folder
click a button to move that folder to a new location (thereby removing all
user plugins in one fel swoop)
re-create an empty plugins folder where it belongs.

At this point  in use you would want to restart lc so that its fresh and
any autostart plugins are out of memory

Next, populate a list of plugins that exist in the moved plugin folder

Choose a plugin, get its short name and store it for later use then..
revcopy it back to the users plugin folder
call revideupdateplugins
call revideopenplugin storedstackname

At this point the just added plugin back in the system, and active

Test as needed, then add another back in and test.

Narrowing down would be faster of course using the binary method others
have mentioned (half at a time) but shouldn't be to bad, and should be
relatively easy to implement.

On Sun, Jul 10, 2016 at 5:52 AM, Alex Tweedly <alex at> wrote:

> [ this isn't yet a well-formed idea, but I'm sure there could be something
> ... ]
> Could there be a special "plugin diagnostic mode" ?
> When it is active, the IDE would
>  - startup one plugin at a time
>  - let you use it / try things out
>  - and then (on some simple command) startup the next one, etc.
> -- Alex.
> On 09/07/2016 22:39, Richard Gaskin wrote:
>> Skip Kimpel wrote:
>> > After some experimentation based upon what Panos suggested, something
>> > in my plugins folder is causing the issue.  Yikes... I have LOTS of
>> > plugins.  Any good way of diagnosing the culprit without doing having
>> > to drop my plugins one by one?
>> By halves.
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the Use-livecode mailing list