Navigator 6.4 alpha 1 is out

Geoff Canyon gcanyon at
Tue Oct 2 02:28:13 CEST 2018

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.


On Mon, Oct 1, 2018 at 4:23 PM Geoff Canyon <gcanyon at> wrote:

> 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 go ahead and special case it. Any
> preference on whether I should call the property "name" but special case to
> display/edit the short name, or instead to call the property "short name"
> but set the name? I lean toward continuing to call the property "name" and
> special case the display, but I'm open to arguments.
> gc
> On Mon, Oct 1, 2018 at 3:54 PM Mark Wieder via use-livecode <
> use-livecode at> wrote:
>> 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_*,
>> rev_g_*, rev_i_*, rev_s_*...) I can't figure out how to fix this for
>> you, so it's in your court:
>> Getting the card list for a stack shows
>> card "name_of_card_1"
>> card "name_of_card_2"
>> etc.
>> Editing the properties to change the card name, the value is also
>> card "name_of_card_1" rather than the short name. If I edit the name and
>> save it, then refresh the card list (problem #1 is that the list should
>> refresh automatically after the change is made), the card is named
>> card "card "name_of_card_1"", adding another "card".
>> So problem #2 is that the card list display shows a "card" identifier
>> and this is erroneously copied into the the value field for the card
>> name, compounded by the fact that when the new card name is saved extra
>> quotes are added to the card name whether or not they're needed.
>> And I verified that it actually does change the card name thusly, so
>> it's not just a display issue.
>> --
>>   Mark Wieder
>>   ahsoftware at
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:

More information about the use-livecode mailing list