Navigator 7.3rc1 is available

Geoff Canyon gcanyon at gmail.com
Wed Jan 30 12:31:21 EST 2019


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



More information about the use-livecode mailing list