Navigator 6.4 alpha 1 is out

[Brian Milby]

You can also link the behaviors folder in the plugins folder to the local copy of the repo behaviors. Then you just need to copy the binary file when you pull the update from the repo.

I go a step further (consolidate it into a single stack) but that is just my experiment.

Thanks,
Brian
On Sep 29, 2018, 7:45 PM -0400, Mark Wieder via use-livecode <use-livecode at lists.runrev.com>, wrote:
> On 09/29/2018 11:42 AM, Geoff Canyon via use-livecode wrote:
> > I just checked, and at least as far as I can tell, this is fixed in my
> > current version of Navigator, and as Matthias says, going back several
> > versions. You can update by getting Navigator here
> > <https://www.dropbox.com/s/kz3zqi4botzglgq/navigator.zip?dl=1>. Or grab it
> > from GitHub <https://github.com/gcanyon/navigator>.
>
> Verified fixed. Here's what messed me up:
>
> I pulled the latest changes from github
> I realized that the binary stack didn't need building
> I sudo copied the plugin into /opt/livecode/...etc
> and then launched the IDE
>
> not realizing I *also* needed to replace the behaviors.
>
> Also, I now realize that I just need to copy the stack into my user
> plugins folder. So user stacks with the same name as system plugin
> stacks will take the place of the builtins? That's a revelation.
>
> --
> Mark Wieder
> ahsoftware at gmail.com
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode