The JADE 2022 release meets tomorrow’s business demands.
Ty Baen-Price
|
HistoricalComments
Brian Johnstone 21/03/2018 2:07:54 PM
@James: Thanks for that. It would probably be best if the autocomplete did a similar tool tip to what it does for method calls. That is, show all the dictionary keys in the tool tip and then use a colour to highlight to indicate which key you're currently specifying - like it does with which parameter you're currently specifying for a method call. James Burnby 21/03/2018 9:10:17 AM @Brian: Actually it is ctrl + 1. The f snuck in there while typing :) Brian Johnstone 20/03/2018 4:04:36 PM Hi @James - Out of interest, what command do you have bound to the Ctrl+F1 shortcut combination to get the details of the dictionary keys for any arbitrary MKD when inside the [ ] brackets? Brian Johnstone 20/03/2018 4:03:35 PM Hi @James - yes the lack of autocomplete suggestions for expressions inside parentheses is the subject of JEDI 123, which I mentioned in my first comment as one example of where autocomplete is not offering the expected suggestions that needs to be fixed before removing the old Ctrl 1/../5 shortcuts. James Burnby 20/03/2018 12:59:29 PM Found a case where I need to use ctrl+2. log(" Firing reference checks for " & myCurrentClass.name & " | " & propertyCount.String & " out of " & totalPropertyCount.String & " | " & (propertyCount / totalPropertyCount).trun <-- Intellisense only gives one option of "true", don't get to see truncated until I press ctrl + 2. James Burnby 16/03/2018 9:01:42 AM I find it priceless to be able to place the cursor between the square brackets of a collection reference and pressing F1. e.g. global.allAccounts[ (press Ctrl + F1). I comment the keys out and use it as a visual reference for the keys. If this is to be removed a bubble help over the collection would be beneficial. Brian Johnstone 12/03/2018 2:50:52 PM Hi @Sam - Ctrl+Space is definitely your friend in this scenario. Also very useful if you've used arrow keys and/or the mouse to position the carat and then want to redisplay the autocomplete suggestions for the current positional context. :) Sam Stokell 12/03/2018 2:13:33 PM The Autocomplete stops working if you start typing something like this: table1.save - then you realise you should have said table2.save so you press backspace until you get to the position between e and 1 and it stops working. I have got a very quick demo video of this if you copy and paste the URL: https://www.screencast.com/t/s1k1Ltsp8 Sam Stokell 12/03/2018 11:38:09 AM I still use the old Ctrl 1/2/3 to just get me a list of what I am wanting to see (Property, Method, Constant). Autocomplete gives the entire list but if I only want to see Constants on that Type I will use Ctrl 3 as an example. Maybe I only want to see those particular constants on that specific type and not the superclasses so I use Ctrl Shift 3. I like using autocomplete most of the time but using Ctrl # is still very useful Ty Baen-Price 12/03/2018 11:11:37 AM If anyone could identify when "autocomplete fails to load" that would be great. I'll give you a start 1) autocomplete does not evaluate expressions. 2) autocomplete does not load when you have a syntax error in the statement autocomplete is analysing. Software Medical Infomatics Limited 12/03/2018 9:43:18 AM Ditto - autocomplete sometimes fails me and then the old fallbacks are useful. But maybe remove these and then address issues that arise in autocomplete. Basically, the old way is a crutch that should be gone. FileVision UK Ltd 10/03/2018 4:08:30 AM As Blake says, I revert to the Ctrl shortcuts when the autocompete fails to load Blake De?Ath 9/03/2018 4:13:29 PM There are times when autocomplete fails to load. Unfortunately I can't give any example off the top of my head. When this happens I revert to Ctrl shortcuts. This is only a temporary problem though, so wouldn't miss them in this scenario. Brian Johnstone 9/03/2018 2:39:42 PM The times when I still use the old Ctrl+1/../5 are those situations where Autocomplete doesn't offer the expected suggestions, such as the example documented in https://jedi.jadeworld.com/hub/#/idea/123. As long as you address issues like that prior to removing the old Ctrl+1/../5 shortcuts then I'd personally have no objections. |
