[ANN] Release 8.2.0 DP-1

[Monte Goulding]

> On 14 Sep 2017, at 2:09 pm, Brian Milby via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> For the autocomplete feature, would discussion be better in a thread here
> or in bugzilla?  Some things that I'm looking at could just be considered
> developer preferences vice actual bugs.  Here are a few examples:

Discuss wherever it suits as long as we put good ideas and issues in bugzilla
> 
> - there is no indication that you are at the end of a list so the down
> arrow will just roll you to the next line
> - same for top of list (not really an issue when it first appears, but if
> going back up it could be)

We have discussed this a bit internally. I did a few things to try and make sure that the completions palette doesn’t get in your way. One is hiding in certain contexts like on mouseMove. Another was this arrow key behavior… but I think maybe I erred here. It’s feasible it’s a legacy from early versions where I had completions being presented as a result of changing the selection and that could have been really frustrating if you were wanting to arrowKey down through your script!
> 
> - the ordering of syntax seems a little off (look at answer for example, I
> would think that "answer prompt" would be first and "answer prompt with
> button1" would come before "answer prompt with button1 or buttons").  The
> idea is to include required terms first and insert the optional terms in a
> similar way (so the optional term without the nested one comes before the
> one including the nested optional term).

Yes there’s certainly some tweaks to be made on that front. There are a couple of reports here:

http://quality.livecode.com/show_bug.cgi?id=20367 <http://quality.livecode.com/show_bug.cgi?id=20367>
This was mainly messages we were considering here and the plan is currently to have a list of messages that are higher priority. That’s quite different to what you are suggesting.

For your idea it may be quite simple to add collect all the variants of a command and give them a priority weighting based on their length (shorter = higher priority)

http://quality.livecode.com/show_bug.cgi?id=20370 <http://quality.livecode.com/show_bug.cgi?id=20370>
This idea of grouping variants if there are a lot and having a way to expose them should also help here

> 
> - in other auto-complete editors (Atom), typing the closing character will
> skip over it if it is the next character instead of adding another set.  So
> when you type " and "" gets inserted.  If you then type a word followed by
> a " you would end up outside of the quoted word instead of with the
> insertion point inside a nested quote.  ["test"| vice "test"|"" where | is
> the insertion point].  Similar situation for [].  Often it would be easier
> to just type the closing character than to reach for the mouse or use an
> arrow key to skip.

I like this idea. Could you please report it.

Cheers

Monte