The first solution is great if you need to enumerate the plugins. The second is
good for just prepending the path before the stack name. Works a peach!
Thanks guys.
>> On Oct 12, 2018, at 12:45 , Paul Hibbert via use-livecode
>> wrote:
>>
>> revIDEPlugins()
>> On Oct 12, 2018, at 12:48 ,
That too!
Bob S
> On Oct 12, 2018, at 12:48 , Mark Wieder via use-livecode
> wrote:
>
> put revenvironmentuserpluginspath()
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage you
That's the ticket! :-)
Bob S
> On Oct 12, 2018, at 12:45 , Paul Hibbert via use-livecode
> wrote:
>
> revIDEPlugins()
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subs
On 10/12/2018 11:18 AM, Bob Sneidar via use-livecode wrote:
Hi all.
You would think all the plugin stacks would be "known" by the IDE, but when I
attempt to open a plugin by name, either short name or the actual file name (without the
path) Livecode cannot find it. There is no SpecialFolderPat
If this is just for your own Dev use then the installed plugins should be in 2
locations, on Mac inside the App bundle;
e.g. /Applications/LiveCode Indy 9.0.1.app/Contents/Tools/Plugins
I’d guess a similar location in Widows inside the App folder.
The user installed plugins should be in the "My
Hi all.
You would think all the plugin stacks would be "known" by the IDE, but when I
attempt to open a plugin by name, either short name or the actual file name
(without the path) Livecode cannot find it. There is no SpecialFolderPath
option for the plugins folder. (Maybe there should be??) S
