Navigator 6.4 alpha 1 is out

classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

Navigator 6.4 alpha 1 is out

Stephen MacLean via use-livecode
As usual, you can get Navigator here
<https://www.dropbox.com/s/kz3zqi4botzglgq/navigator.zip?dl=1>. Or grab it
from GitHub <https://github.com/gcanyon/navigator>.

Phew! I discovered a brutal bug in Navigator while coding this update.
Everyone should either update, or avoid the "Save All" and "Save
Stackfiles" popup menu options. The code that iterated over the stackFiles
of a stack to save them all didn't have a test for existence, and thus if
any stackFiles were deleted, but still in the stackFiles property of the
stack being saved, then the loop would die (silently, because of the "rev"
prefix) and not save the remaining stackFiles. I have no idea how I managed
to work on Navigator for the past eight months, using this feature *all the
time*, and not run into this before. But in this case, I ended up having to
code -- and lose -- the functionality listed below *twice* before I twigged
to what was happening. :-(

In any case, the "Save All" function now checks for existence on each stack
before attempting to do anything with it, and if any are missing, will
offer to update the stackFiles property to remove the ones that are missing.

As an aside, does the IDE have any sort of equivalent function? i.e. "run
through the stackFiles of this stack and save them all"?

NEW FEATURES

The "Edit Colors" option on the popup menu now works -- it worked before on
the Properties menu.

Completely reworked the mouse-targeting options:
 -- Choose Color
 -- Stack menu -> the mouseStack
 -- Action menu -> Bookmark -> MouseControl

You no longer need to hold down the option key while using these commands
-- I believe this made these functions useless under Linux, as well as
making them harder to use in general. Instead, as soon as you trigger the
command, Navigator displays a cross-hair. Mouse over the
color/control/stack you want to select, and click, and the selection is
done.

Updated the mouseStack command so that when Navigator displays the current
card of the stack you select, the control the crosshair was over when you
made the selection is hilited in Navigator's list. This has been an awesome
feature for me, I hope it delights you as well, and I'm looking to further
enhance this.

Fixed (I believe) an error where sometimes Navigator would think that it
was still dragging even after the mouse is up. It was tricky to get this to
happen, so we'll see...

Fixed an error in the placement of the drag and drop controls when dragging
from one Navigator to another. This had previously been fixed for dragging
within Navigator, but I just found the remaining issue.

Improved Navigator's handling of hilites when cloning, deleting, and
dragging and dropping, but it's by no means perfect yet. There was an issue
where Navigator's record of what lines are hilited wouldn't be updated
after cloning or deleting controls. This could lead to weird dragging
responses, and this has now been fixed.

Also, you should find that when dragging a control, hilites are somewhat
retained -- as long as the control's long id doesn't change, it should
continue to be hilited. This means dragging controls into or out of groups
breaks this functionality, and situations where the control is copied will
break it as well.

regards,

gc
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Navigator 6.4 alpha 1 is out

Stephen MacLean 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 open the color editor.
2. If the property is true/false, it will simply toggle between those two
values.
3. If the property has a defined set of values (the style of a button, for
example) then the list of styles will pop up for you to select. If I have
missed any of these in Navigator's configuration, let me know.
4. If the property is defined as single-line in Navigator's configuration,
it will edit in-line in the property editor. This is also a configuration
in Navigator, so if I have missed any of these, let me know.
5. If none of the above apply, the standard Navigator editor window will
open.

gc

On Mon, Sep 24, 2018 at 8:19 PM Geoff Canyon <[hidden email]> wrote:

> As usual, you can get Navigator here
> <https://www.dropbox.com/s/kz3zqi4botzglgq/navigator.zip?dl=1>. Or grab
> it from GitHub <https://github.com/gcanyon/navigator>.
>
> Phew! I discovered a brutal bug in Navigator while coding this update.
> Everyone should either update, or avoid the "Save All" and "Save
> Stackfiles" popup menu options. The code that iterated over the stackFiles
> of a stack to save them all didn't have a test for existence, and thus if
> any stackFiles were deleted, but still in the stackFiles property of the
> stack being saved, then the loop would die (silently, because of the "rev"
> prefix) and not save the remaining stackFiles. I have no idea how I managed
> to work on Navigator for the past eight months, using this feature *all the
> time*, and not run into this before. But in this case, I ended up having to
> code -- and lose -- the functionality listed below *twice* before I twigged
> to what was happening. :-(
>
> In any case, the "Save All" function now checks for existence on each
> stack before attempting to do anything with it, and if any are missing,
> will offer to update the stackFiles property to remove the ones that are
> missing.
>
> As an aside, does the IDE have any sort of equivalent function? i.e. "run
> through the stackFiles of this stack and save them all"?
>
> NEW FEATURES
>
> The "Edit Colors" option on the popup menu now works -- it worked before
> on the Properties menu.
>
> Completely reworked the mouse-targeting options:
>  -- Choose Color
>  -- Stack menu -> the mouseStack
>  -- Action menu -> Bookmark -> MouseControl
>
> You no longer need to hold down the option key while using these commands
> -- I believe this made these functions useless under Linux, as well as
> making them harder to use in general. Instead, as soon as you trigger the
> command, Navigator displays a cross-hair. Mouse over the
> color/control/stack you want to select, and click, and the selection is
> done.
>
> Updated the mouseStack command so that when Navigator displays the current
> card of the stack you select, the control the crosshair was over when you
> made the selection is hilited in Navigator's list. This has been an awesome
> feature for me, I hope it delights you as well, and I'm looking to further
> enhance this.
>
> Fixed (I believe) an error where sometimes Navigator would think that it
> was still dragging even after the mouse is up. It was tricky to get this to
> happen, so we'll see...
>
> Fixed an error in the placement of the drag and drop controls when
> dragging from one Navigator to another. This had previously been fixed for
> dragging within Navigator, but I just found the remaining issue.
>
> Improved Navigator's handling of hilites when cloning, deleting, and
> dragging and dropping, but it's by no means perfect yet. There was an issue
> where Navigator's record of what lines are hilited wouldn't be updated
> after cloning or deleting controls. This could lead to weird dragging
> responses, and this has now been fixed.
>
> Also, you should find that when dragging a control, hilites are somewhat
> retained -- as long as the control's long id doesn't change, it should
> continue to be hilited. This means dragging controls into or out of
> groups breaks this functionality, and situations where the control is
> copied will break it as well.
>
> regards,
>
> gc
>
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Navigator 6.4 alpha 1 is out

Stephen MacLean via use-livecode
In reply to this post by Stephen MacLean via use-livecode
On 09/24/2018 08:19 PM, Geoff Canyon via use-livecode wrote:
> As usual, you can get Navigator here
> <https://www.dropbox.com/s/kz3zqi4botzglgq/navigator.zip?dl=1>. Or grab it
> from GitHub <https://github.com/gcanyon/navigator>.

Eek! Cloning a card from the contextual menu pastes the new card into
Navigator instead of into the topstack.

--
  Mark Wieder
  [hidden email]

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Navigator 6.4 alpha 1 is out

Stephen MacLean 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 <
[hidden email]> wrote:

> On 09/24/2018 08:19 PM, Geoff Canyon via use-livecode wrote:
> > As usual, you can get Navigator here
> > <https://www.dropbox.com/s/kz3zqi4botzglgq/navigator.zip?dl=1>. Or grab
> it
> > from GitHub <https://github.com/gcanyon/navigator>.
>
> Eek! Cloning a card from the contextual menu pastes the new card into
> Navigator instead of into the topstack.
>
> --
>   Mark Wieder
>   [hidden email]
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Navigator 6.4 alpha 1 is out

Stephen MacLean 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 <[hidden email] <mailto:[hidden email]>>:
>
> 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 <https://quality.livecode.com/show_bug.cgi?id=21509>
>
> On Fri, Sep 28, 2018 at 9:56 AM Mark Wieder via use-livecode <
> [hidden email]> wrote:
>
>> On 09/24/2018 08:19 PM, Geoff Canyon via use-livecode wrote:
>>> As usual, you can get Navigator here
>>> <https://www.dropbox.com/s/kz3zqi4botzglgq/navigator.zip?dl=1>. Or grab
>> it
>>> from GitHub <https://github.com/gcanyon/navigator>.
>>
>> Eek! Cloning a card from the contextual menu pastes the new card into
>> Navigator instead of into the topstack.
>>
>> --
>>  Mark Wieder
>>  [hidden email]
>>
>> _______________________________________________
>> use-livecode mailing list
>> [hidden email]
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

Matthias Rebbe
Tel +49 5741 310000
https://matthiasrebbe.eu <https://matthiasrebbe.eu/>‌

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Navigator 6.4 alpha 1 is out

Stephen MacLean 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
<https://www.dropbox.com/s/kz3zqi4botzglgq/navigator.zip?dl=1>. Or grab it
from GitHub <https://github.com/gcanyon/navigator>.

gc

>
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Navigator 6.4 alpha 1 is out

Stephen MacLean 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
> <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
  [hidden email]

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Navigator 6.4 alpha 1 is out

Stephen MacLean 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 29, 2018, 7:45 PM -0400, Mark Wieder via use-livecode <[hidden email]>, 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
> [hidden email]
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Navigator 6.4 alpha 1 is out

Stephen MacLean 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'm still amazed that user
plugins override the builtins.

--
  Mark Wieder
  [hidden email]

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Navigator 6.4 alpha 1 is out

Stephen MacLean via use-livecode
In reply to this post by Stephen MacLean via use-livecode
On Sat, Sep 29, 2018 at 4:45 PM Mark Wieder via use-livecode <
[hidden email]> 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 multiple times
through the interface, so everything is a behavior.

I just got the external commands code working properly again, so that
folder might become necessary to the installation as well.

gc
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Navigator 6.4 alpha 1 is out

Stephen MacLean via use-livecode
In reply to this post by Stephen MacLean via use-livecode
On 09/24/2018 08:19 PM, Geoff Canyon via use-livecode wrote:
> As usual, you can get Navigator here
> <https://www.dropbox.com/s/kz3zqi4botzglgq/navigator.zip?dl=1>. Or grab it
> from GitHub <https://github.com/gcanyon/navigator>.

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
  [hidden email]

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Navigator 6.4 alpha 1 is out

Stephen MacLean 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 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 <
[hidden email]> wrote:

> On 09/24/2018 08:19 PM, Geoff Canyon via use-livecode wrote:
> > As usual, you can get Navigator here
> > <https://www.dropbox.com/s/kz3zqi4botzglgq/navigator.zip?dl=1>. Or grab
> it
> > from GitHub <https://github.com/gcanyon/navigator>.
>
> 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
>   [hidden email]
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Navigator 6.4 alpha 1 is out

Stephen MacLean 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

On Mon, Oct 1, 2018 at 4:23 PM Geoff Canyon <[hidden email]> 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 <
> [hidden email]> wrote:
>
>> On 09/24/2018 08:19 PM, Geoff Canyon via use-livecode wrote:
>> > As usual, you can get Navigator here
>> > <https://www.dropbox.com/s/kz3zqi4botzglgq/navigator.zip?dl=1>. Or
>> grab it
>> > from GitHub <https://github.com/gcanyon/navigator>.
>>
>> 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
>>   [hidden email]
>>
>> _______________________________________________
>> use-livecode mailing list
>> [hidden email]
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Navigator 6.4 alpha 1 is out

Stephen MacLean 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 days so I'm going to use it for a bit before releasing it.

Yeah, to my thinking that's the way it should work. I think the only
time I want the "name" of something rather than the "short name" is when
I need to differentiate between different types of objects, such as when
I'm iterating through the child controls of a group. Otherwise I just
grab the short name, edit it, and put it back where I found it.

--
  Mark Wieder
  [hidden email]

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Navigator 6.4 alpha 1 is out

Stephen MacLean 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 <
[hidden email]> wrote:

> 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 days so I'm going to use it for a bit before releasing it.
>
> Yeah, to my thinking that's the way it should work. I think the only
> time I want the "name" of something rather than the "short name" is when
> I need to differentiate between different types of objects, such as when
> I'm iterating through the child controls of a group. Otherwise I just
> grab the short name, edit it, and put it back where I found it.
>
> --
>   Mark Wieder
>   [hidden email]
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Navigator 6.4 alpha 1 is out

Stephen MacLean via use-livecode


> On Oct 1, 2018, at 18:00 , Geoff Canyon via use-livecode <[hidden email]> 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 limits.

Bob S


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode