Re: Navigator 6.4 alpha 1 is out

2018-10-02 Thread Bob Sneidar via use-livecode
> On Oct 1, 2018, at 18:00 , Geoff Canyon via use-livecode > wrote: > > Agreed. It's annoying that my code is now uglier because of this one > special case -- although to be fair, Navigator is a fifteen-year-old plate > of spaghetti. And now you've added some cheese! WHOOPS! Sorry, off limit

Re: Navigator 6.4 alpha 1 is out

2018-10-01 Thread Geoff Canyon via use-livecode
Agreed. It's annoying that my code is now uglier because of this one special case -- although to be fair, Navigator is a fifteen-year-old plate of spaghetti. On Mon, Oct 1, 2018 at 5:54 PM Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: > On 10/01/2018 05:28 PM, Geoff Canyon

Re: Navigator 6.4 alpha 1 is out

2018-10-01 Thread Mark Wieder via use-livecode
On 10/01/2018 05:28 PM, Geoff Canyon via use-livecode wrote: I went ahead and fixed this. In my working copy of Navigator the property is displayed as being "name" but displays the short name. Editing it sets the name. I made some fundamental changes to the way Navigator works over the past few d

Re: Navigator 6.4 alpha 1 is out

2018-10-01 Thread Geoff Canyon via use-livecode
I went ahead and fixed this. In my working copy of Navigator the property is displayed as being "name" but displays the short name. Editing it sets the name. I made some fundamental changes to the way Navigator works over the past few days so I'm going to use it for a bit before releasing it. gc

Re: Navigator 6.4 alpha 1 is out

2018-10-01 Thread Geoff Canyon via use-livecode
Yeah (sigh) it's down to the fact that you can *get* the short name of something, but you can't *set* the short name of something. So I need to special case that one property :-( It's been an annoyance forever, but I always put off fixing it because it offends me. But since you brought it up I'll

Re: Navigator 6.4 alpha 1 is out

2018-10-01 Thread Mark Wieder via use-livecode
On 09/24/2018 08:19 PM, Geoff Canyon via use-livecode wrote: As usual, you can get Navigator here . Or grab it from GitHub . Due to the huge number of behavior scripts (rev_b_*, rev_c_*, rev_f_*,

Re: Navigator 6.4 alpha 1 is out

2018-09-29 Thread Geoff Canyon via use-livecode
On Sat, Sep 29, 2018 at 4:45 PM Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: > > not realizing I *also* needed to replace the behaviors. > Yeah, the full installation of Navigator always requires the updated stack and the behaviors folder. The Navigator stack is replicated

Re: Navigator 6.4 alpha 1 is out

2018-09-29 Thread Mark Wieder via use-livecode
On 09/29/2018 04:58 PM, Brian Milby via use-livecode wrote: 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. Nice. I hadn't thought of linking the folder. I'

Re: Navigator 6.4 alpha 1 is out

2018-09-29 Thread Brian Milby via use-livecode
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

Re: Navigator 6.4 alpha 1 is out

2018-09-29 Thread Mark Wieder via use-livecode
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

Re: Navigator 6.4 alpha 1 is out

2018-09-29 Thread Geoff Canyon via use-livecode
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 . Or grab it from GitHub

Re: Navigator 6.4 alpha 1 is out

2018-09-29 Thread Matthias Rebbe via use-livecode
Hi, yes, you´ve fixed that. I am running here 6.3 alpha 1 and with that version the cloned card is pasted in the original stack. Regards, Matthias > Am 29.09.2018 um 19:50 schrieb Geoff Canyon via use-livecode > mailto:use-livecode@lists.runrev.com>>: > > Bah -- I thought I had fixed this, le

Re: Navigator 6.4 alpha 1 is out

2018-09-29 Thread Geoff Canyon via use-livecode
Bah -- I thought I had fixed this, let me take a look. FYI, I filed a bug for this (to me) odd behavior, but it looks like it's a "feature". https://quality.livecode.com/show_bug.cgi?id=21509 On Fri, Sep 28, 2018 at 9:56 AM Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: > On

Re: Navigator 6.4 alpha 1 is out

2018-09-28 Thread Mark Wieder via use-livecode
On 09/24/2018 08:19 PM, Geoff Canyon via use-livecode wrote: As usual, you can get Navigator here . Or grab it from GitHub . Eek! Cloning a card from the contextual menu pastes the new card into

Re: Navigator 6.4 alpha 1 is out

2018-09-24 Thread Geoff Canyon via use-livecode
I forgot -- I also added in-line editing of properties identified as single-line in Navigator's property editor. Meaning: 1. If the property is "colors" (this would only be displayed if you add colors to the control's properties in Navigator's preferences dialog) then Navigator will immediately op

Navigator 6.4 alpha 1 is out

2018-09-24 Thread Geoff Canyon via use-livecode
As usual, you can get Navigator here . Or grab it from GitHub . Phew! I discovered a brutal bug in Navigator while coding this update. Everyone should either update, or avoid the "Save All" and "Sav

Navigator 6.4 alpha 1 is out

2018-09-24 Thread Geoff Canyon via use-livecode
As usual, you can get Navigator here . Or grab it from GitHub . Phew! I discovered a brutal bug in Navigator while coding this update. Everyone should either update, or avoid the "Save All" and "Sav