Navigator 7.3rc1 is available

chipsm at themartinz.com chipsm at themartinz.com
Wed Jan 30 14:49:45 EST 2019


Sorry I didn't understand what you were saying. 
Thanks for the reply.
I really like the Pug-in and it's great.

Sincerely,

Clarence Martin
Email: Chipsm at themartinz.com
Cell: 626 696-5561

-----Original Message-----
From: use-livecode <use-livecode-bounces at lists.runrev.com> On Behalf Of
Geoff Canyon via use-livecode
Sent: Wednesday, January 30, 2019 11:38 AM
To: How to use LiveCode <use-livecode at lists.runrev.com>
Cc: Geoff Canyon <gcanyon at gmail.com>
Subject: Re: Navigator 7.3rc1 is available

Yep, that's exactly what I said -- when you open in a new Navigator, the
target is a specific container (a group in this case). Under those
circumstances Navigator doesn't try to select controls in Livecode, or mimic
Livecode's selections, because the group might not be visible or selectable.
Like I said in the bug, I'll add a setting and protection for Navigator to
try to mimic anyway


On Wed, Jan 30, 2019 at 10:40 AM Clarence Martin via use-livecode <
use-livecode at lists.runrev.com> wrote:

> I created a video for you to see but it is being check by the LiveCode 
> list admin for content because of its size.
> Here is a link to my OneDrive folder containing the video:
> https://1drv.ms/v/s!AmMnOdWPxdzK6jkkp3Kn8m7HIwm_
> You can download and view it from there. I hoe this explains my comments.
>
> Sincerely,
>
> Clarence Martin
> Email: Chipsm at themartinz.com
> Cell: 626 696-5561
>
> -----Original Message-----
> From: use-livecode <use-livecode-bounces at lists.runrev.com> On Behalf 
> Of Geoff Canyon via use-livecode
> Sent: Wednesday, January 30, 2019 9:31 AM
> To: How to use LiveCode <use-livecode at lists.runrev.com>
> Cc: Geoff Canyon <gcanyon at gmail.com>
> Subject: Re: Navigator 7.3rc1 is available
>
> On Wed, Jan 30, 2019 at 5:09 AM Clarence Martin via use-livecode < 
> use-livecode at lists.runrev.com> wrote:
>
> > Ji Geoff,
> > I am responding to you 7.3rc1 and this is probably true about the 
> > other releases too.
> > I noticed that if I open a group in a New Navigator window, the 
> > first Navigator window has lost control over the group that precipitated
it.
> > The new Navigator Window Group items don't respond to any items that 
> > are clicked or highlighted.
> > Also, if I open a group for editing, the Navigator window does not 
> > respond to any items that are clicked or highlighted in the Group 
> > Edit
> window.
> > I can live with this now that I know  about this behavior, but I 
> > don't know if anyone has pointed this out to you.
> >
>
> I'm not sure what you mean by "lost control". I followed these steps:
>
> 1. Created a Livecode window, added three buttons, and grouped them.
> 2. Opened Navigator. It shows the stack, the card, the group, and the 
> three buttons.
> 3. Right-click on the group in Navigator, and select "Browse Controls" 
> on the popup menu. Navigator shows the stack, the group, and the buttons.
> 4. Right-click the first button in Navigator and select Rename... on 
> the popup menu. Navigator opens the dialog and I successfully rename 
> the button.
> 5. Right-click the group in Navigator and select Open in New Navigator 
> on the popup menu. Navigator opens a new window showing the same controls.
> 6. In the new Navigator, right-click the second button and select
Rename...
> on the popup menu. Navigator opens the dialog and I successfully 
> rename the button.
> 7. In the original Navigator, right-click the third button and select 
> Rename... on the popup menu. Navigator opens the dialog and I 
> successfully rename the button.
>
> So Navigator still knows what controls it's supposed to display, 
> displays them, and works with them.
>
> Wait -- do you mean highlighting? As in, select controls in Navigator, 
> and they become selected in Livecode, and vice versa? If so, that was 
> originally a function of Navigator displaying "this card of the 
> topstack"
> because it's impossible to select controls in a card that isn't being 
> displayed. At some point there was a bug in Navigator where the code 
> was trying to match highlights for anything displayed in Navigator. 
> Any time the highlighting failed, Navigator's code would die silently 
> because it's considered and IDE stack by the IDE. It didn't throw 
> visible errors, but it means that any code after that doesn't get 
> executed, so I fixed it to the way it was originally: if you select 
> "the topstack" on the Target
> (crosshair) menu, Navigator will display whatever is frontmost in 
> Livecode, and match highlights.
>
> I added this, in case you are talking about highlights:
> https://github.com/gcanyon/navigator/issues/32
>
> If that's not what you're talking about, let me know.
>
> thanks,
>
> gc
> _______________________________________________
> 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
>
>
> _______________________________________________
> 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
>
_______________________________________________
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





More information about the Use-livecode mailing list